Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9fb2a993f66aa64207d26ded1b74ab890509b5b08a65a531a3d0600d63b622d

Tx prefix hash: b74539b9adfe80412dea8ae765afa2ce1def2aa1c835ec6991f0fc1b6b21d8a8
Tx public key: 83691d8d8515ea7d35596f9ccb04126483be52344bed9d585c005b1e2937493a
Timestamp: 1708114329 Timestamp [UCT]: 2024-02-16 20:12:09 Age [y:d:h:m:s]: 01:047:01:34:41
Block: 959015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294660 RingCT/type: yes/0
Extra: 0183691d8d8515ea7d35596f9ccb04126483be52344bed9d585c005b1e2937493a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 640c13a4de9dea87a7cf7b33852eb386545d054b2c782eca57d20f3d55de5b8a 0.600000000000 1418534 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": 959025, "vin": [ { "gen": { "height": 959015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "640c13a4de9dea87a7cf7b33852eb386545d054b2c782eca57d20f3d55de5b8a" } } ], "extra": [ 1, 131, 105, 29, 141, 133, 21, 234, 125, 53, 89, 111, 156, 203, 4, 18, 100, 131, 190, 82, 52, 75, 237, 157, 88, 92, 0, 91, 30, 41, 55, 73, 58, 2, 17, 0, 0, 0, 3, 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