Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a3dce032df8671e112f40eabf7e54288cd7bab2db3944868013c049fd4e7f6e

Tx prefix hash: a3dc5861e5fcdab60514f35ff0390e2d21f438d8ff5d92cf51350754c2ed4a5a
Tx public key: e23e24054fc5e522d313ef774bb2a31b0ec942a055201b935d74d0691834fa9c
Timestamp: 1726283579 Timestamp [UCT]: 2024-09-14 03:12:59 Age [y:d:h:m:s]: 00:225:20:59:24
Block: 1109644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161289 RingCT/type: yes/0
Extra: 01e23e24054fc5e522d313ef774bb2a31b0ec942a055201b935d74d0691834fa9c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f732f628e53f066ce4c219ce3f08124baf858ecf41e05aebd92976aa876f09cc 0.600000000000 1587975 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": 1109654, "vin": [ { "gen": { "height": 1109644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f732f628e53f066ce4c219ce3f08124baf858ecf41e05aebd92976aa876f09cc" } } ], "extra": [ 1, 226, 62, 36, 5, 79, 197, 229, 34, 211, 19, 239, 119, 75, 178, 163, 27, 14, 201, 66, 160, 85, 32, 27, 147, 93, 116, 208, 105, 24, 52, 250, 156, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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