Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 144b591bc24ffdfdb404114a3c03eba7abdfe8c11896b387ad335ad6ab7a498e

Tx prefix hash: 9861490615ae2eaea7668780f6cd1696dd926dc352f7792bcea247e6aa45db9e
Tx public key: ac0daad8f3e988a52ce1a6c76077376dcd8f82ad5e5f0ff81ad0ef04c481e747
Timestamp: 1684655406 Timestamp [UCT]: 2023-05-21 07:50:06 Age [y:d:h:m:s]: 02:173:01:23:41
Block: 764790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 643478 RingCT/type: yes/0
Extra: 01ac0daad8f3e988a52ce1a6c76077376dcd8f82ad5e5f0ff81ad0ef04c481e74702110000000933af99f4000000000000000000

1 output(s) for total of 1.794458554000 dcy

stealth address amount amount idx
00: f91ca97de639edb3e1e035245c8bc43f32bfb22254b6d8ae72ac9a6d8490ffa1 1.794458554000 1213743 of 0

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": 764800, "vin": [ { "gen": { "height": 764790 } } ], "vout": [ { "amount": 1794458554, "target": { "key": "f91ca97de639edb3e1e035245c8bc43f32bfb22254b6d8ae72ac9a6d8490ffa1" } } ], "extra": [ 1, 172, 13, 170, 216, 243, 233, 136, 165, 44, 225, 166, 199, 96, 119, 55, 109, 205, 143, 130, 173, 94, 95, 15, 248, 26, 208, 239, 4, 196, 129, 231, 71, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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