Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78428236b0baa94a8a2d2a0661da6788f83b391211a041b7252d68e94c1cb3a1

Tx prefix hash: 45b1cf50dfab916916b0f776f5c4af66e7c1b33aa831f9e5082e775d68921d94
Tx public key: cee5a9fe8fbf2d5c3aee3cabe09af50c6b8c745b3c54099cbd26b4e589cc2cb2
Timestamp: 1764115598 Timestamp [UCT]: 2025-11-26 00:06:38 Age [y:d:h:m:s]: 00:001:09:59:27
Block: 1420169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1013 RingCT/type: yes/0
Extra: 01cee5a9fe8fbf2d5c3aee3cabe09af50c6b8c745b3c54099cbd26b4e589cc2cb20211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5d5b442003e4b2ed3706827201235fa751c14146bf9f3daf61b0d8b26f55668 0.600000000000 1908710 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": 1420179, "vin": [ { "gen": { "height": 1420169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5d5b442003e4b2ed3706827201235fa751c14146bf9f3daf61b0d8b26f55668" } } ], "extra": [ 1, 206, 229, 169, 254, 143, 191, 45, 92, 58, 238, 60, 171, 224, 154, 245, 12, 107, 140, 116, 91, 60, 84, 9, 156, 189, 38, 180, 229, 137, 204, 44, 178, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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