Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e528220ef243ccc5319ea481cf0db6be428ff222e5e0a1c2c81f81d1c5381d0f

Tx prefix hash: 0bb0d460fd1faa8e6a0010dc3c2bcc979e63777a7cbc743790a468ae4842a71d
Tx public key: e33fb4b2681d9bd684b9c9b1f523645da7951b4020a6345851817972a2513406
Timestamp: 1709047891 Timestamp [UCT]: 2024-02-27 15:31:31 Age [y:d:h:m:s]: 01:109:19:55:43
Block: 966770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339438 RingCT/type: yes/0
Extra: 01e33fb4b2681d9bd684b9c9b1f523645da7951b4020a6345851817972a25134060211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18029f8d91674cce45daacd2beb4277f25ced0dc82b1d06a149f012f8d27d397 0.600000000000 1426541 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": 966780, "vin": [ { "gen": { "height": 966770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18029f8d91674cce45daacd2beb4277f25ced0dc82b1d06a149f012f8d27d397" } } ], "extra": [ 1, 227, 63, 180, 178, 104, 29, 155, 214, 132, 185, 201, 177, 245, 35, 100, 93, 167, 149, 27, 64, 32, 166, 52, 88, 81, 129, 121, 114, 162, 81, 52, 6, 2, 17, 0, 0, 0, 5, 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