Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14c67fec158706b70d180514dc5e36d2944202b42788652e9d54450975e11d09

Tx prefix hash: 36c54999c14e9ac2618f6687c0ede655891a70d8f781e5fda8fb54b229893817
Tx public key: 71a23de5322313cb1b1be1f0bde5ce6c5797cd0b14b9538a840ea60aa2eebd6a
Timestamp: 1739529006 Timestamp [UCT]: 2025-02-14 10:30:06 Age [y:d:h:m:s]: 00:289:22:23:04
Block: 1219027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204985 RingCT/type: yes/0
Extra: 0171a23de5322313cb1b1be1f0bde5ce6c5797cd0b14b9538a840ea60aa2eebd6a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d4ff8954fe19e412be2730da27bec861a36bcfce1d1de2206bb18e994074cb4 0.600000000000 1705850 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": 1219037, "vin": [ { "gen": { "height": 1219027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d4ff8954fe19e412be2730da27bec861a36bcfce1d1de2206bb18e994074cb4" } } ], "extra": [ 1, 113, 162, 61, 229, 50, 35, 19, 203, 27, 27, 225, 240, 189, 229, 206, 108, 87, 151, 205, 11, 20, 185, 83, 138, 132, 14, 166, 10, 162, 238, 189, 106, 2, 17, 0, 0, 0, 3, 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