Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ab213657068a68b2d3738ea5efcaee3594a3cde12e7d8d4e39189b3e19618ae

Tx prefix hash: 0c28aef03262f7ca6cb9d79705e2dc9b88644e1f1fbe9c6153772d65700183a6
Tx public key: 232633972f287bc6178e5eaf7f5ef9abdfaad074852b471860482bbffabb3a2e
Timestamp: 1710675486 Timestamp [UCT]: 2024-03-17 11:38:06 Age [y:d:h:m:s]: 01:005:07:22:14
Block: 980269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264759 RingCT/type: yes/0
Extra: 01232633972f287bc6178e5eaf7f5ef9abdfaad074852b471860482bbffabb3a2e0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 063f382e7229881e7e1aabf9988aea7ad6afeac83d320c24da99d7546e975b10 0.600000000000 1440334 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": 980279, "vin": [ { "gen": { "height": 980269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "063f382e7229881e7e1aabf9988aea7ad6afeac83d320c24da99d7546e975b10" } } ], "extra": [ 1, 35, 38, 51, 151, 47, 40, 123, 198, 23, 142, 94, 175, 127, 94, 249, 171, 223, 170, 208, 116, 133, 43, 71, 24, 96, 72, 43, 191, 250, 187, 58, 46, 2, 17, 0, 0, 0, 7, 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