Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3bbfe3d075f7c7d95a4e6202c095b5bf8cfe22357bc1083ffbdcaa25614ab4c

Tx prefix hash: c0926912ae644f2b70c952fe896092f9ad946d824acc901f7e7f5de97a69ab3c
Tx public key: 06fd03d566d42ed4befae0916393b461ee1ae1535aa3c02bd6d936219e3669ec
Timestamp: 1761273688 Timestamp [UCT]: 2025-10-24 02:41:28 Age [y:d:h:m:s]: 00:064:03:25:31
Block: 1396632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45905 RingCT/type: yes/0
Extra: 0106fd03d566d42ed4befae0916393b461ee1ae1535aa3c02bd6d936219e3669ec021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a108f694bb8b8cfb606ed66d155a2419d7400f7904b01cfc1ad057ebc0b2bb0 0.600000000000 1884919 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": 1396642, "vin": [ { "gen": { "height": 1396632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a108f694bb8b8cfb606ed66d155a2419d7400f7904b01cfc1ad057ebc0b2bb0" } } ], "extra": [ 1, 6, 253, 3, 213, 102, 212, 46, 212, 190, 250, 224, 145, 99, 147, 180, 97, 238, 26, 225, 83, 90, 163, 192, 43, 214, 217, 54, 33, 158, 54, 105, 236, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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