Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d34851e1bf2fba3bb7d93233da6263b269b473a09125af4e4a7170e9668a779

Tx prefix hash: 4e432f9165691bc67f1b616591cf73aa59923fee8da6317cc9e958a8445be338
Tx public key: 4c59eb729c8971ec27dca3a2308ed2f24cf7d56cb246ccd8ccfca9f89229357e
Timestamp: 1745131738 Timestamp [UCT]: 2025-04-20 06:48:58 Age [y:d:h:m:s]: 00:199:08:53:20
Block: 1265397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140193 RingCT/type: yes/0
Extra: 014c59eb729c8971ec27dca3a2308ed2f24cf7d56cb246ccd8ccfca9f89229357e0211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9d35784d2c3c8e8fc38d9f500973845cd7614d3e78b1d5db881d7311eba9222 0.600000000000 1752604 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": 1265407, "vin": [ { "gen": { "height": 1265397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9d35784d2c3c8e8fc38d9f500973845cd7614d3e78b1d5db881d7311eba9222" } } ], "extra": [ 1, 76, 89, 235, 114, 156, 137, 113, 236, 39, 220, 163, 162, 48, 142, 210, 242, 76, 247, 213, 108, 178, 70, 204, 216, 204, 252, 169, 248, 146, 41, 53, 126, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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