Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 454c36e10f05f3d3bdede4f62bb7a10db1fb2c7ba9e660e51cfb08f0ac5c751c

Tx prefix hash: d92bdd5e1b19f6313508a641f441679ef19aa3c44749abf6fa0151b4ea8cc064
Tx public key: 3ac32f8498159e66085d3b006a1e2767ae0fd1fa3aa420b8b5d0e6bc9cd210f4
Timestamp: 1704579922 Timestamp [UCT]: 2024-01-06 22:25:22 Age [y:d:h:m:s]: 01:089:04:25:07
Block: 929691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324853 RingCT/type: yes/0
Extra: 013ac32f8498159e66085d3b006a1e2767ae0fd1fa3aa420b8b5d0e6bc9cd210f40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9333dfdb23f18d7858e391b164977b5fb3cc71f6aba279c3a29c6f733914fa7e 0.600000000000 1387567 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": 929701, "vin": [ { "gen": { "height": 929691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9333dfdb23f18d7858e391b164977b5fb3cc71f6aba279c3a29c6f733914fa7e" } } ], "extra": [ 1, 58, 195, 47, 132, 152, 21, 158, 102, 8, 93, 59, 0, 106, 30, 39, 103, 174, 15, 209, 250, 58, 164, 32, 184, 181, 208, 230, 188, 156, 210, 16, 244, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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