Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73a15e96adcef88859407f3264330568176abe143f2eb1b58dd8ece0cf5d7d3c

Tx prefix hash: 5a4a8a68e0546dc96e74e195040268c4aa7af8a0d39d9299a394fe978b4d23d1
Tx public key: 0d86febc9c8e676b06e1476b7adc54143c716eaa14e1ef86dfb141105b3f3f07
Timestamp: 1704244535 Timestamp [UCT]: 2024-01-03 01:15:35 Age [y:d:h:m:s]: 01:017:11:11:12
Block: 926917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273793 RingCT/type: yes/0
Extra: 010d86febc9c8e676b06e1476b7adc54143c716eaa14e1ef86dfb141105b3f3f070211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea05c83351a192b5ccde0cba44c76c9869719706660b2f390ecb801be293ee55 0.600000000000 1384717 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": 926927, "vin": [ { "gen": { "height": 926917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea05c83351a192b5ccde0cba44c76c9869719706660b2f390ecb801be293ee55" } } ], "extra": [ 1, 13, 134, 254, 188, 156, 142, 103, 107, 6, 225, 71, 107, 122, 220, 84, 20, 60, 113, 110, 170, 20, 225, 239, 134, 223, 177, 65, 16, 91, 63, 63, 7, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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