Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6237f59bfdc28b3c768986c6ef4d9d2ff94d2e0413f52d10337575aa8f470713

Tx prefix hash: f9f32edae55c87821075258b7a601acff78ec1d28632ce1bcbfbc91e01a8541c
Tx public key: 16e76026e6c6e797f689968614a527caa65e5b2f7d6e0812a8dbbffed9af52f9
Timestamp: 1708237776 Timestamp [UCT]: 2024-02-18 06:29:36 Age [y:d:h:m:s]: 01:036:20:22:35
Block: 960040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287347 RingCT/type: yes/0
Extra: 0116e76026e6c6e797f689968614a527caa65e5b2f7d6e0812a8dbbffed9af52f90211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770152b546390c22468703b597e75eaaaa296ae87adc8fecf2cd6def90e9c912 0.600000000000 1419599 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": 960050, "vin": [ { "gen": { "height": 960040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770152b546390c22468703b597e75eaaaa296ae87adc8fecf2cd6def90e9c912" } } ], "extra": [ 1, 22, 231, 96, 38, 230, 198, 231, 151, 246, 137, 150, 134, 20, 165, 39, 202, 166, 94, 91, 47, 125, 110, 8, 18, 168, 219, 191, 254, 217, 175, 82, 249, 2, 17, 0, 0, 0, 3, 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