Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1fd76274da39efd583dc97cd757a22b9d3f31ad3143dd2b35a4517f4fd2f88f

Tx prefix hash: 96ae6d3c6ae94bb0afcae7bfe673f6489d81fb6df44b28b12f71045503dd7904
Tx public key: 9ac7d8c3ec4e9d370e54357cef485c431f830cf8dccaac87dca8722e338a9bb0
Timestamp: 1760961151 Timestamp [UCT]: 2025-10-20 11:52:31 Age [y:d:h:m:s]: 00:019:22:39:11
Block: 1394043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14262 RingCT/type: yes/0
Extra: 019ac7d8c3ec4e9d370e54357cef485c431f830cf8dccaac87dca8722e338a9bb002110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a42ebc8591cafe0c3aaf4b4f654c7ef13d29025a4b997e5a41b59d05b47a405 0.600000000000 1882310 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": 1394053, "vin": [ { "gen": { "height": 1394043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a42ebc8591cafe0c3aaf4b4f654c7ef13d29025a4b997e5a41b59d05b47a405" } } ], "extra": [ 1, 154, 199, 216, 195, 236, 78, 157, 55, 14, 84, 53, 124, 239, 72, 92, 67, 31, 131, 12, 248, 220, 202, 172, 135, 220, 168, 114, 46, 51, 138, 155, 176, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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