Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4818404793cb98d99165bc041270b56f403823c113f3873843523d0f359b3389

Tx prefix hash: 0867be3dcb67bcf86bd00f30616a5d1ec974fddc5201eb0371f3a3f654573c69
Tx public key: 6d96b71e9000979c0b821a3163c72d1dcb4203d3c73abf29671d1cd552a8fc6c
Timestamp: 1696820784 Timestamp [UCT]: 2023-10-09 03:06:24 Age [y:d:h:m:s]: 01:189:19:03:45
Block: 865594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396689 RingCT/type: yes/0
Extra: 016d96b71e9000979c0b821a3163c72d1dcb4203d3c73abf29671d1cd552a8fc6c02110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.831625479000 dcy

stealth address amount amount idx
00: 451b131a4cff4b3bcbc08b9b706852940eee4237ca75eec6a765a208f8693350 0.831625479000 1320132 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": 865604, "vin": [ { "gen": { "height": 865594 } } ], "vout": [ { "amount": 831625479, "target": { "key": "451b131a4cff4b3bcbc08b9b706852940eee4237ca75eec6a765a208f8693350" } } ], "extra": [ 1, 109, 150, 183, 30, 144, 0, 151, 156, 11, 130, 26, 49, 99, 199, 45, 29, 203, 66, 3, 211, 199, 58, 191, 41, 103, 29, 28, 213, 82, 168, 252, 108, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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