Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c839478349b90cb0a0b13c5f664287f503b93fa6d97efa19423616f1e35ce220

Tx prefix hash: 83cb856dfcd9fa59dfdeb62a9403405fd1961ac2b98a8689e683671dff8e793f
Tx public key: ffda5e3ccfc04bad97f06e577264c599833e3982136f4ea1fe1e6a68f216f3f0
Timestamp: 1702561693 Timestamp [UCT]: 2023-12-14 13:48:13 Age [y:d:h:m:s]: 01:339:02:53:24
Block: 912981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501229 RingCT/type: yes/0
Extra: 01ffda5e3ccfc04bad97f06e577264c599833e3982136f4ea1fe1e6a68f216f3f002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81b88775ff39fad2997617533450db7edf4b2f80ba5db5d4fb7b939d5e66d840 0.600000000000 1370219 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": 912991, "vin": [ { "gen": { "height": 912981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81b88775ff39fad2997617533450db7edf4b2f80ba5db5d4fb7b939d5e66d840" } } ], "extra": [ 1, 255, 218, 94, 60, 207, 192, 75, 173, 151, 240, 110, 87, 114, 100, 197, 153, 131, 62, 57, 130, 19, 111, 78, 161, 254, 30, 106, 104, 242, 22, 243, 240, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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