Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9ba75ab4725c544763233f8f6d695374f78a7bdd3e2002a4758ed66e7d340db

Tx prefix hash: 9aa0b7dc005be0126f20c3ceb48dfd644dc64337cdd2cf11a4566a309b5a8200
Tx public key: 971b9d92da67a5e6f387ca691ab5cd4ebdf5b3a210edb4b9a0ace471b3dfaf20
Timestamp: 1732871002 Timestamp [UCT]: 2024-11-29 09:03:22 Age [y:d:h:m:s]: 00:197:07:45:07
Block: 1164163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140805 RingCT/type: yes/0
Extra: 01971b9d92da67a5e6f387ca691ab5cd4ebdf5b3a210edb4b9a0ace471b3dfaf20021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f57f00757146af5d420acf2254a2c65229331770867f6e5bee1893ec28c2639f 0.600000000000 1649836 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": 1164173, "vin": [ { "gen": { "height": 1164163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f57f00757146af5d420acf2254a2c65229331770867f6e5bee1893ec28c2639f" } } ], "extra": [ 1, 151, 27, 157, 146, 218, 103, 165, 230, 243, 135, 202, 105, 26, 181, 205, 78, 189, 245, 179, 162, 16, 237, 180, 185, 160, 172, 228, 113, 179, 223, 175, 32, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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