Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ad9b4a0e6225d2824a2e75d9244b43a99d4444439e3971503652b9357ec98cd

Tx prefix hash: 9d63fa7b80c6afe8391f0a2e9ccee690ebf982c729474133efe160ba28204a0a
Tx public key: 0771e1b8b852c518665187c91b9edd3470a2b13a0934fd707adb636e2049afc5
Timestamp: 1707565876 Timestamp [UCT]: 2024-02-10 11:51:16 Age [y:d:h:m:s]: 01:065:17:09:59
Block: 954460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308019 RingCT/type: yes/0
Extra: 010771e1b8b852c518665187c91b9edd3470a2b13a0934fd707adb636e2049afc50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b6ffe0060cc7e7a8ea05a6c63e987db730b6bdd033e043c24e9284faa55a680 0.600000000000 1413740 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": 954470, "vin": [ { "gen": { "height": 954460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b6ffe0060cc7e7a8ea05a6c63e987db730b6bdd033e043c24e9284faa55a680" } } ], "extra": [ 1, 7, 113, 225, 184, 184, 82, 197, 24, 102, 81, 135, 201, 27, 158, 221, 52, 112, 162, 177, 58, 9, 52, 253, 112, 122, 219, 99, 110, 32, 73, 175, 197, 2, 17, 0, 0, 0, 2, 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