Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d65170aea5a95be3fcb1806ecbfd7e8c8cb2fe13e7c673eaeee9d4f442ddb51

Tx prefix hash: 77d3b0e172cb84e33ae1285a015d09de81b9e49bf02c57c20790eaf2abeb28db
Tx public key: e461181396eaafbaf6352ab8abe7488fc7a7e6c6832a78ef75e5a305c8b7899f
Timestamp: 1766200253 Timestamp [UCT]: 2025-12-20 03:10:53 Age [y:d:h:m:s]: 00:003:07:28:14
Block: 1437441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2360 RingCT/type: yes/0
Extra: 01e461181396eaafbaf6352ab8abe7488fc7a7e6c6832a78ef75e5a305c8b7899f0211000000087b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ddd5729b55e775ea00fd8e75d95d2eebd341735afefd88e093e5b7172ae5252 0.600000000000 1926248 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": 1437451, "vin": [ { "gen": { "height": 1437441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ddd5729b55e775ea00fd8e75d95d2eebd341735afefd88e093e5b7172ae5252" } } ], "extra": [ 1, 228, 97, 24, 19, 150, 234, 175, 186, 246, 53, 42, 184, 171, 231, 72, 143, 199, 167, 230, 198, 131, 42, 120, 239, 117, 229, 163, 5, 200, 183, 137, 159, 2, 17, 0, 0, 0, 8, 123, 30, 81, 172, 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