Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5003577e1e5b282027bc0ab40320a751c0cf1eea7e1ba177c76a3a513d17555

Tx prefix hash: f1d3c40f376cdf1f0cbe0cc857348a3d987714b59a5ae4ae942972827cb01093
Tx public key: 8da8a179da35378e92c6ee542c7aed62713345e6c520d75b2f05bba2afeb07a4
Timestamp: 1731136863 Timestamp [UCT]: 2024-11-09 07:21:03 Age [y:d:h:m:s]: 00:050:10:58:29
Block: 1149801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36090 RingCT/type: yes/0
Extra: 018da8a179da35378e92c6ee542c7aed62713345e6c520d75b2f05bba2afeb07a4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1cf0e7fd680d4e332d8152d0ae01796e4d38d84814e4f50f328343e2cd897b3 0.600000000000 1634964 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": 1149811, "vin": [ { "gen": { "height": 1149801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1cf0e7fd680d4e332d8152d0ae01796e4d38d84814e4f50f328343e2cd897b3" } } ], "extra": [ 1, 141, 168, 161, 121, 218, 53, 55, 142, 146, 198, 238, 84, 44, 122, 237, 98, 113, 51, 69, 230, 197, 32, 215, 91, 47, 5, 187, 162, 175, 235, 7, 164, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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