Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d666a4d6ff11c4feb36885ee46e94c74e27acf91eb1e5de5c4ea011f49ac1cb

Tx prefix hash: 14e62ce674bf71972689dc9f3f3b6514e8d97dac9fc04bc53ee3b3135c268216
Tx public key: 5434c9556a646d2299d25731d911df4fc8614f5714b4069c6d986849022c0551
Timestamp: 1756067969 Timestamp [UCT]: 2025-08-24 20:39:29 Age [y:d:h:m:s]: 00:093:20:15:20
Block: 1353660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67014 RingCT/type: yes/0
Extra: 015434c9556a646d2299d25731d911df4fc8614f5714b4069c6d986849022c05510211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e67ff0b943302e4623ab6c0367d1d5e6e7c0851c4e4417fe19b4550211f4711c 0.600000000000 1841637 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": 1353670, "vin": [ { "gen": { "height": 1353660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e67ff0b943302e4623ab6c0367d1d5e6e7c0851c4e4417fe19b4550211f4711c" } } ], "extra": [ 1, 84, 52, 201, 85, 106, 100, 109, 34, 153, 210, 87, 49, 217, 17, 223, 79, 200, 97, 79, 87, 20, 180, 6, 156, 109, 152, 104, 73, 2, 44, 5, 81, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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