Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d20a182d1091b1c1a1650ec84519ebfee50ab6fd1ff4c2bd51b2555986f3408c

Tx prefix hash: 304a4ca5877deb6d2dd5b8d27b932e9afe93547ec507c9ebfd38c10d5c5836fa
Tx public key: 2c798c315a9e5e18c20047d35787ae5fb0554afc3bb72bd456caa9ec63f83338
Timestamp: 1710567775 Timestamp [UCT]: 2024-03-16 05:42:55 Age [y:d:h:m:s]: 00:344:03:50:12
Block: 979381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246028 RingCT/type: yes/0
Extra: 012c798c315a9e5e18c20047d35787ae5fb0554afc3bb72bd456caa9ec63f833380211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72ac7de4002bf6e5c9470f68e6153791d9e2a564de209c66c224bc9bcdff023e 0.600000000000 1439414 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": 979391, "vin": [ { "gen": { "height": 979381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72ac7de4002bf6e5c9470f68e6153791d9e2a564de209c66c224bc9bcdff023e" } } ], "extra": [ 1, 44, 121, 140, 49, 90, 158, 94, 24, 194, 0, 71, 211, 87, 135, 174, 95, 176, 85, 74, 252, 59, 183, 43, 212, 86, 202, 169, 236, 99, 248, 51, 56, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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