Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90061f051e1c8828dd167536060618f4236cb68b6f2705aeae4c9811d90c5a50

Tx prefix hash: 193931babb01390d908d039ab720f0cc1287eb17ac29eb645421f8cf83614eda
Tx public key: cac01d9e5e0f74e963571a31bfa9b02003b9f71df5c8f17fd6272cd7abec6764
Timestamp: 1766016444 Timestamp [UCT]: 2025-12-18 00:07:24 Age [y:d:h:m:s]: 00:020:04:59:36
Block: 1435913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14474 RingCT/type: yes/0
Extra: 01cac01d9e5e0f74e963571a31bfa9b02003b9f71df5c8f17fd6272cd7abec676402110000000770609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eca24b917823c4d58c19db2fa69224d0e8ffc49c9b56f6fe53b2a946b0a18a6d 0.600000000000 1924718 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": 1435923, "vin": [ { "gen": { "height": 1435913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eca24b917823c4d58c19db2fa69224d0e8ffc49c9b56f6fe53b2a946b0a18a6d" } } ], "extra": [ 1, 202, 192, 29, 158, 94, 15, 116, 233, 99, 87, 26, 49, 191, 169, 176, 32, 3, 185, 247, 29, 245, 200, 241, 127, 214, 39, 44, 215, 171, 236, 103, 100, 2, 17, 0, 0, 0, 7, 112, 96, 157, 3, 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