Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24e0b25c05a6b70a42677f8afb3e698f5ecbb811a4cf44959e8f802ac4856c8a

Tx prefix hash: 144aa756070a8d3cf038cd1662e9d6e5b08cacaf7716c18d5a1bd786fdb6234a
Tx public key: ef4ff155c4292e81d48ae42abc398eb487cb4c23c94b9c5cbe6ff7807409b5d2
Timestamp: 1736194971 Timestamp [UCT]: 2025-01-06 20:22:51 Age [y:d:h:m:s]: 00:162:13:17:43
Block: 1191686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115887 RingCT/type: yes/0
Extra: 01ef4ff155c4292e81d48ae42abc398eb487cb4c23c94b9c5cbe6ff7807409b5d20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36be861bfc1f78be7c3e1c26f82673e7eec68991913d0608ceda87a04b24898b 0.600000000000 1678227 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": 1191696, "vin": [ { "gen": { "height": 1191686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36be861bfc1f78be7c3e1c26f82673e7eec68991913d0608ceda87a04b24898b" } } ], "extra": [ 1, 239, 79, 241, 85, 196, 41, 46, 129, 212, 138, 228, 42, 188, 57, 142, 180, 135, 203, 76, 35, 201, 75, 156, 92, 190, 111, 247, 128, 116, 9, 181, 210, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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