Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66a23f3d354662396e75fac7f1335d07a7604164118e92078d538d7d18d5cc82

Tx prefix hash: 6224f8a25a0cdd4f84b247abd106b4e9b3c4c9aca4c249bba154b725bda87bb1
Tx public key: a734a7c958fdc266d4de832caade09869ce863004febd36ce79c3faff3a8726b
Timestamp: 1580895924 Timestamp [UCT]: 2020-02-05 09:45:24 Age [y:d:h:m:s]: 04:325:22:51:41
Block: 59214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124261 RingCT/type: yes/0
Extra: 01a734a7c958fdc266d4de832caade09869ce863004febd36ce79c3faff3a8726b0211000000c217786bcf000000000000000000

1 output(s) for total of 390.661179149000 dcy

stealth address amount amount idx
00: d422471dc0c212875d988376287dc6f2decc22c545966892b2f3e4fe7f86a325 390.661179149000 109306 of 0

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": 59224, "vin": [ { "gen": { "height": 59214 } } ], "vout": [ { "amount": 390661179149, "target": { "key": "d422471dc0c212875d988376287dc6f2decc22c545966892b2f3e4fe7f86a325" } } ], "extra": [ 1, 167, 52, 167, 201, 88, 253, 194, 102, 212, 222, 131, 44, 170, 222, 9, 134, 156, 232, 99, 0, 79, 235, 211, 108, 231, 156, 63, 175, 243, 168, 114, 107, 2, 17, 0, 0, 0, 194, 23, 120, 107, 207, 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