Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9222ec5c98a7a24712dc1f691014fb5ac1b8496e24895efc2f119cc82ccd87f9

Tx prefix hash: c0e4bf0273015eaf30794b54d1361f2dafcbf2ad603142c6f3eb73194a02451e
Tx public key: 201f42ccf044526e78fec6367bc3fc52e6c7c583d436a0fecdf7b4fb6b930797
Timestamp: 1749589267 Timestamp [UCT]: 2025-06-10 21:01:07 Age [y:d:h:m:s]: 00:158:13:13:32
Block: 1302304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111004 RingCT/type: yes/0
Extra: 01201f42ccf044526e78fec6367bc3fc52e6c7c583d436a0fecdf7b4fb6b930797021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 097cb30f682e970b375d9778e54672bcfd20a5d612e8150afc3cc9ad00e62cf2 0.600000000000 1789873 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": 1302314, "vin": [ { "gen": { "height": 1302304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "097cb30f682e970b375d9778e54672bcfd20a5d612e8150afc3cc9ad00e62cf2" } } ], "extra": [ 1, 32, 31, 66, 204, 240, 68, 82, 110, 120, 254, 198, 54, 123, 195, 252, 82, 230, 199, 197, 131, 212, 54, 160, 254, 205, 247, 180, 251, 107, 147, 7, 151, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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