Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 58df13ec3839e2db7fc36c2fa4b9efdde113acf9d86f93476724251a9a75bd1b

Tx prefix hash: 47f493083c1a867f8e4598391ec618bcf4509c1aab01d64c6288df461f8eeaa9
Tx public key: b94976e08a837be6a82f59b255ae4a7d750e80ef06b8c4c4cbbdf7febd7d6310
Timestamp: 1742066425 Timestamp [UCT]: 2025-03-15 19:20:25 Age [y:d:h:m:s]: 00:292:07:49:57
Block: 1240045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206711 RingCT/type: yes/0
Extra: 01b94976e08a837be6a82f59b255ae4a7d750e80ef06b8c4c4cbbdf7febd7d63100211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2a632acdc6acd2dcc90c108304793d12863898012ec39c9a595018a6de5ea11 0.600000000000 1727010 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1240055, "vin": [ { "gen": { "height": 1240045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2a632acdc6acd2dcc90c108304793d12863898012ec39c9a595018a6de5ea11" } } ], "extra": [ 1, 185, 73, 118, 224, 138, 131, 123, 230, 168, 47, 89, 178, 85, 174, 74, 125, 117, 14, 128, 239, 6, 184, 196, 196, 203, 189, 247, 254, 189, 125, 99, 16, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8