Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 722eaab5395ede6efc028db411de02a10583ee96dade7167512f0483b6ab20ad

Tx prefix hash: cd2ad8acd3d7fa52d8947cc342c828105ac8b87892a1cae65c96f8122c8a9a4e
Tx public key: 4af910f9a508955956e3c0c51a3af8e3d86a33caac83f1dc9c4deab88f31cbff
Timestamp: 1725112106 Timestamp [UCT]: 2024-08-31 13:48:26 Age [y:d:h:m:s]: 00:290:22:49:39
Block: 1099933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207726 RingCT/type: yes/0
Extra: 014af910f9a508955956e3c0c51a3af8e3d86a33caac83f1dc9c4deab88f31cbff02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 642f28802cc95104a10a46e5b1536a98c5ad44b942400499276f3f7d78315409 0.600000000000 1575902 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": 1099943, "vin": [ { "gen": { "height": 1099933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "642f28802cc95104a10a46e5b1536a98c5ad44b942400499276f3f7d78315409" } } ], "extra": [ 1, 74, 249, 16, 249, 165, 8, 149, 89, 86, 227, 192, 197, 26, 58, 248, 227, 216, 106, 51, 202, 172, 131, 241, 220, 156, 77, 234, 184, 143, 49, 203, 255, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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