Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 689768068379308b5e729862882cac1c0b8095889f5825ea91d929e27a67ec1d

Tx prefix hash: cd840459e709c56f18a3e0b5408173278d145d9cac876540b1f14f3133440efd
Tx public key: e791c7de65c9822bf5b3237263aa5659898e14a2978d5a1a5a99185d58e2be72
Timestamp: 1703454447 Timestamp [UCT]: 2023-12-24 21:47:27 Age [y:d:h:m:s]: 01:176:18:12:50
Block: 920386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387375 RingCT/type: yes/0
Extra: 01e791c7de65c9822bf5b3237263aa5659898e14a2978d5a1a5a99185d58e2be7202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36b450d6a23405fb1d4ba7c287afab55a8d1e3473212dea2c09048dc0b726b33 0.600000000000 1378064 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": 920396, "vin": [ { "gen": { "height": 920386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36b450d6a23405fb1d4ba7c287afab55a8d1e3473212dea2c09048dc0b726b33" } } ], "extra": [ 1, 231, 145, 199, 222, 101, 201, 130, 43, 245, 179, 35, 114, 99, 170, 86, 89, 137, 142, 20, 162, 151, 141, 90, 26, 90, 153, 24, 93, 88, 226, 190, 114, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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