Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9f5f8d738a0b61beb23793780bce7ce908f1112a83079300ea0ee0257889a7

Tx prefix hash: a4c071b8d9e16eee2f68fd5a18c11c5b737733ac71a6e378ae907e8b34b4b8dc
Tx public key: 0059f4b8e105048cf5912731b477784afec84710e9b6b836062dfc6fdeced3fc
Timestamp: 1749410969 Timestamp [UCT]: 2025-06-08 19:29:29 Age [y:d:h:m:s]: 00:166:03:53:28
Block: 1300831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116442 RingCT/type: yes/0
Extra: 010059f4b8e105048cf5912731b477784afec84710e9b6b836062dfc6fdeced3fc02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16b73c67b30374f524d0a15b54cbeb50dc1437ed4354171564fcdc41f5fc9345 0.600000000000 1788382 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": 1300841, "vin": [ { "gen": { "height": 1300831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16b73c67b30374f524d0a15b54cbeb50dc1437ed4354171564fcdc41f5fc9345" } } ], "extra": [ 1, 0, 89, 244, 184, 225, 5, 4, 140, 245, 145, 39, 49, 180, 119, 120, 74, 254, 200, 71, 16, 233, 182, 184, 54, 6, 45, 252, 111, 222, 206, 211, 252, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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