Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559cef3b68b5331a33dd79221a7ef474abb1ca9cd1f91e28cb2b9e2f28a45c02

Tx prefix hash: b9bd386f06e0df0198b734b1069939be3fefb3e7459c69cb2b32b2584524161e
Tx public key: d3a0de11b97328a7e03fc68de80628f3a2c72448adb7d3b3b1ed655b6d9e5ff6
Timestamp: 1713255222 Timestamp [UCT]: 2024-04-16 08:13:42 Age [y:d:h:m:s]: 00:355:13:47:26
Block: 1001619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254205 RingCT/type: yes/0
Extra: 01d3a0de11b97328a7e03fc68de80628f3a2c72448adb7d3b3b1ed655b6d9e5ff60211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4141173415a28e56174c5a8f6209489a309fa14fd14ba9d0ca632ec6502e6df 0.600000000000 1462125 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": 1001629, "vin": [ { "gen": { "height": 1001619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4141173415a28e56174c5a8f6209489a309fa14fd14ba9d0ca632ec6502e6df" } } ], "extra": [ 1, 211, 160, 222, 17, 185, 115, 40, 167, 224, 63, 198, 141, 232, 6, 40, 243, 162, 199, 36, 72, 173, 183, 211, 179, 177, 237, 101, 91, 109, 158, 95, 246, 2, 17, 0, 0, 0, 2, 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