Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b8fc3c3e09cc316b573eae45c600b6d161e16d0cce38650dbf9efe0c9de29e0

Tx prefix hash: da586eb3a5ff26f949aadbc9eff044e32183d2a54fbe7163db16397a04ac6919
Tx public key: 9fa26672a7397aa5cbbbe1c7025e3644ac96e4efb8cb1e5311933a7c31a4baee
Timestamp: 1729363175 Timestamp [UCT]: 2024-10-19 18:39:35 Age [y:d:h:m:s]: 00:145:09:42:09
Block: 1135170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103706 RingCT/type: yes/0
Extra: 019fa26672a7397aa5cbbbe1c7025e3644ac96e4efb8cb1e5311933a7c31a4baee021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae3d0bbc94a23ddb5a6a880ff73d0de6b0460a29939ce3556e69d8ce51412e43 0.600000000000 1618501 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": 1135180, "vin": [ { "gen": { "height": 1135170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae3d0bbc94a23ddb5a6a880ff73d0de6b0460a29939ce3556e69d8ce51412e43" } } ], "extra": [ 1, 159, 162, 102, 114, 167, 57, 122, 165, 203, 187, 225, 199, 2, 94, 54, 68, 172, 150, 228, 239, 184, 203, 30, 83, 17, 147, 58, 124, 49, 164, 186, 238, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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