Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e797d2169b11c66a9711788641b78a10afd75a205e3dd00a916fae448b16b207

Tx prefix hash: f98d2dae75e01c420d0c53163a1767b7a63b06d1e1b84ce38f328e60f145c9b2
Tx public key: 6ac20a83d700481ab2b4f201db5bc8b16caed9d4f326e4f88bf4dc6644158eb0
Timestamp: 1712945663 Timestamp [UCT]: 2024-04-12 18:14:23 Age [y:d:h:m:s]: 01:026:05:46:05
Block: 999043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279740 RingCT/type: yes/0
Extra: 016ac20a83d700481ab2b4f201db5bc8b16caed9d4f326e4f88bf4dc6644158eb00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8365f38ffa5a061ccf6e500aa0f6eb8f58d34ebc681c4b79b042ce24e6f4610e 0.600000000000 1459519 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": 999053, "vin": [ { "gen": { "height": 999043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8365f38ffa5a061ccf6e500aa0f6eb8f58d34ebc681c4b79b042ce24e6f4610e" } } ], "extra": [ 1, 106, 194, 10, 131, 215, 0, 72, 26, 178, 180, 242, 1, 219, 91, 200, 177, 108, 174, 217, 212, 243, 38, 228, 248, 139, 244, 220, 102, 68, 21, 142, 176, 2, 17, 0, 0, 0, 3, 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