Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18b209f3386851df5ce6b0750afdf3b646a024748d968810ee6101f55b5b2e35

Tx prefix hash: dde1caa491f2ec912a50b9b4e598efa6b31bb45708f3bce647a3b460b2fe491b
Tx public key: 5e84094bbf75ea193a1496c9ddb43043fa95bf9b4b7ee96c1731183ff65252ea
Timestamp: 1713464865 Timestamp [UCT]: 2024-04-18 18:27:45 Age [y:d:h:m:s]: 01:023:12:49:53
Block: 1003360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277791 RingCT/type: yes/0
Extra: 015e84094bbf75ea193a1496c9ddb43043fa95bf9b4b7ee96c1731183ff65252ea021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56edd3d5c104c4928e943675ac736b32b1cd4c8de58d5d27a754ca40ba5040e6 0.600000000000 1463890 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": 1003370, "vin": [ { "gen": { "height": 1003360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56edd3d5c104c4928e943675ac736b32b1cd4c8de58d5d27a754ca40ba5040e6" } } ], "extra": [ 1, 94, 132, 9, 75, 191, 117, 234, 25, 58, 20, 150, 201, 221, 180, 48, 67, 250, 149, 191, 155, 75, 126, 233, 108, 23, 49, 24, 63, 246, 82, 82, 234, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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