Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59b84df731531e079b02a101b3aecfd823dd869c6e95714a4375daefe5b17f32

Tx prefix hash: 98758bfb35b0d60188ee13c75e4dc44866bc8f9cc689443d6bf6b40cd97aa108
Tx public key: 32bfe99ce3b7f747e3582f91252cbccb9aba57486328706a71580d96294b5adb
Timestamp: 1708156804 Timestamp [UCT]: 2024-02-17 08:00:04 Age [y:d:h:m:s]: 01:038:05:19:27
Block: 959359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288345 RingCT/type: yes/0
Extra: 0132bfe99ce3b7f747e3582f91252cbccb9aba57486328706a71580d96294b5adb0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b037ae4172523a8c1cd5c365ab761add1ffcacfbbf3a372a8e494f40b063bd9 0.600000000000 1418894 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": 959369, "vin": [ { "gen": { "height": 959359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b037ae4172523a8c1cd5c365ab761add1ffcacfbbf3a372a8e494f40b063bd9" } } ], "extra": [ 1, 50, 191, 233, 156, 227, 183, 247, 71, 227, 88, 47, 145, 37, 44, 188, 203, 154, 186, 87, 72, 99, 40, 112, 106, 113, 88, 13, 150, 41, 75, 90, 219, 2, 17, 0, 0, 0, 4, 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