Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768812e0a1f8b458e11987939a1e28dd1dbd90a80f45bbe7c22cddb7653163e8

Tx prefix hash: 0e55740c540ad3da51cb01a032c63f02f2954bfcc6cde38e1a89d3a7317e6be1
Tx public key: ed9953970f5a1af35d2aae422dedaa6eddf79ad1ac69c93ca346ca06faadb892
Timestamp: 1577613303 Timestamp [UCT]: 2019-12-29 09:55:03 Age [y:d:h:m:s]: 05:042:15:45:12
Block: 34285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1180183 RingCT/type: yes/0
Extra: 01ed9953970f5a1af35d2aae422dedaa6eddf79ad1ac69c93ca346ca06faadb8920211000000094fb58672000000000000000000

1 output(s) for total of 472.498483132000 dcy

stealth address amount amount idx
00: 2c4f4b295b698e356b5b6c73165aee0a9d659fa798ddbaa458357dcda297693c 472.498483132000 57668 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": 34295, "vin": [ { "gen": { "height": 34285 } } ], "vout": [ { "amount": 472498483132, "target": { "key": "2c4f4b295b698e356b5b6c73165aee0a9d659fa798ddbaa458357dcda297693c" } } ], "extra": [ 1, 237, 153, 83, 151, 15, 90, 26, 243, 93, 42, 174, 66, 45, 237, 170, 110, 221, 247, 154, 209, 172, 105, 201, 60, 163, 70, 202, 6, 250, 173, 184, 146, 2, 17, 0, 0, 0, 9, 79, 181, 134, 114, 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