Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df823057f2958e924eec0ee1b8896274b813044a66365634e17f39047074fa83

Tx prefix hash: 64ceefba8ead262360a26522d4f4d531393f2aeb8d76c3a261c2e71b75105e45
Tx public key: 50c5e9a246d1557efec3fdf17abc8dc5fd32c1918d1969543749b024bfe68e1e
Timestamp: 1758889742 Timestamp [UCT]: 2025-09-26 12:29:02 Age [y:d:h:m:s]: 00:050:23:37:37
Block: 1376871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36494 RingCT/type: yes/0
Extra: 0150c5e9a246d1557efec3fdf17abc8dc5fd32c1918d1969543749b024bfe68e1e02110000000597baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53ff96485bda0e90e0d9b8c20d30b7a69b6a25921fd08295a485173f1ca2c308 0.600000000000 1864962 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": 1376881, "vin": [ { "gen": { "height": 1376871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53ff96485bda0e90e0d9b8c20d30b7a69b6a25921fd08295a485173f1ca2c308" } } ], "extra": [ 1, 80, 197, 233, 162, 70, 209, 85, 126, 254, 195, 253, 241, 122, 188, 141, 197, 253, 50, 193, 145, 141, 25, 105, 84, 55, 73, 176, 36, 191, 230, 142, 30, 2, 17, 0, 0, 0, 5, 151, 186, 249, 34, 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