Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62dae19b2a21ec953bf6be75c390abdcef8e02579e9e8087a847d365f7e42e5b

Tx prefix hash: bfdb9c37c5cd8529263be09c7faca7b58caca9872d300996f32d61aafe690067
Tx public key: 8ac76e0169531376c2f917eb5007a895f9d28b1e4a67cb204a70d3d8fa74ba03
Timestamp: 1765916786 Timestamp [UCT]: 2025-12-16 20:26:26 Age [y:d:h:m:s]: 00:016:02:48:14
Block: 1435085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11552 RingCT/type: yes/0
Extra: 018ac76e0169531376c2f917eb5007a895f9d28b1e4a67cb204a70d3d8fa74ba0302110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df0cfc336afaa217bbc0d664f28d2e7ef50bbe005adc8f58354a32cbbae76ef9 0.600000000000 1923882 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": 1435095, "vin": [ { "gen": { "height": 1435085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df0cfc336afaa217bbc0d664f28d2e7ef50bbe005adc8f58354a32cbbae76ef9" } } ], "extra": [ 1, 138, 199, 110, 1, 105, 83, 19, 118, 194, 249, 23, 235, 80, 7, 168, 149, 249, 210, 139, 30, 74, 103, 203, 32, 74, 112, 211, 216, 250, 116, 186, 3, 2, 17, 0, 0, 0, 5, 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