Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3fe17d0a8ada94a5e508dfe87e35a1356b269cf099d6808425b77b15433827c

Tx prefix hash: 0ade6ee2b1c3a89b9b74ad770b7ad3a2f32b0cb6db994cc6b12394f072e972ae
Tx public key: 9a780e238717361a8a356edd0331a7b731f62eab628b9d47ec3066d3899c22c9
Timestamp: 1721800786 Timestamp [UCT]: 2024-07-24 05:59:46 Age [y:d:h:m:s]: 00:253:19:59:28
Block: 1072475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181326 RingCT/type: yes/0
Extra: 019a780e238717361a8a356edd0331a7b731f62eab628b9d47ec3066d3899c22c9021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fa63f3adcb6b6caffdab85c2430fa75c78e125105217aee006e781a035effcd 0.600000000000 1544946 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": 1072485, "vin": [ { "gen": { "height": 1072475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fa63f3adcb6b6caffdab85c2430fa75c78e125105217aee006e781a035effcd" } } ], "extra": [ 1, 154, 120, 14, 35, 135, 23, 54, 26, 138, 53, 110, 221, 3, 49, 167, 183, 49, 246, 46, 171, 98, 139, 157, 71, 236, 48, 102, 211, 137, 156, 34, 201, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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