Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62bc9820a4e256b81834ac91a1109647d485cdf3052275263f27b1508121ed00

Tx prefix hash: b39298ef29c3880129414e9e5abe90c72dd9e27beacd43e68de2484f4e3b16b4
Tx public key: 8976813f898281b8c40fa8edd7e68b377acf59075c8a5aa5d151aa10db0de6e9
Timestamp: 1710312470 Timestamp [UCT]: 2024-03-13 06:47:50 Age [y:d:h:m:s]: 01:065:11:01:39
Block: 977250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307794 RingCT/type: yes/0
Extra: 018976813f898281b8c40fa8edd7e68b377acf59075c8a5aa5d151aa10db0de6e90211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f989ffdb30ca0e65c45a812b0942e902af5e3b2f035f61aa4e597b9fd511e80 0.600000000000 1437251 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": 977260, "vin": [ { "gen": { "height": 977250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f989ffdb30ca0e65c45a812b0942e902af5e3b2f035f61aa4e597b9fd511e80" } } ], "extra": [ 1, 137, 118, 129, 63, 137, 130, 129, 184, 196, 15, 168, 237, 215, 230, 139, 55, 122, 207, 89, 7, 92, 138, 90, 165, 209, 81, 170, 16, 219, 13, 230, 233, 2, 17, 0, 0, 0, 8, 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