Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0ef2da6c7c1d9721e0933d933057e739df1d7da80bb98049b6036a8d9e97204

Tx prefix hash: f68d1bf4c348965bd72b974d10f739051cb1fdfc61d90095a33a0d47b3bf9529
Tx public key: 20a8ce9cb3b6d12f0f4cb25b747a8e2257acd75a2f293984016a10a389d647c1
Timestamp: 1709337836 Timestamp [UCT]: 2024-03-02 00:03:56 Age [y:d:h:m:s]: 00:328:09:58:38
Block: 969164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235043 RingCT/type: yes/0
Extra: 0120a8ce9cb3b6d12f0f4cb25b747a8e2257acd75a2f293984016a10a389d647c10211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65bf58b6b1555d0c06853180cd739ca920834b471485af77daf003743a077231 0.600000000000 1428993 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": 969174, "vin": [ { "gen": { "height": 969164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65bf58b6b1555d0c06853180cd739ca920834b471485af77daf003743a077231" } } ], "extra": [ 1, 32, 168, 206, 156, 179, 182, 209, 47, 15, 76, 178, 91, 116, 122, 142, 34, 87, 172, 215, 90, 47, 41, 57, 132, 1, 106, 16, 163, 137, 214, 71, 193, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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