Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62655fff421377390efde7303fd70538099aea15e7a7d8d598fd972caa0c90b3

Tx prefix hash: 8ea1d7d8342320f4fed8324ec144e847328058c223aacbc201c274e1a0643022
Tx public key: 828f6765c838d2a151dd5113206b8202f3a6fc7dadd1b4d9a36aa9a318f797d8
Timestamp: 1703107135 Timestamp [UCT]: 2023-12-20 21:18:55 Age [y:d:h:m:s]: 01:348:19:03:14
Block: 917526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508144 RingCT/type: yes/0
Extra: 01828f6765c838d2a151dd5113206b8202f3a6fc7dadd1b4d9a36aa9a318f797d802110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51cb8399dc90a21e6899f65382ef258b66ccd069863ce8835fae92d0c7654cd6 0.600000000000 1375108 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": 917536, "vin": [ { "gen": { "height": 917526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51cb8399dc90a21e6899f65382ef258b66ccd069863ce8835fae92d0c7654cd6" } } ], "extra": [ 1, 130, 143, 103, 101, 200, 56, 210, 161, 81, 221, 81, 19, 32, 107, 130, 2, 243, 166, 252, 125, 173, 209, 180, 217, 163, 106, 169, 163, 24, 247, 151, 216, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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