Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69778d1a89ee5979575f2849daa99d39e5aecc969577c7d9079dd6300e4fe7c3

Tx prefix hash: 4f0a080c08c25974be8378e0c36499797c82125e593890dfeb683c2fb08012df
Tx public key: c5b17fbab5b416c6e1b70be2574ad995bd652770d6f7068cceaa1f3a5f007d9f
Timestamp: 1754856378 Timestamp [UCT]: 2025-08-10 20:06:18 Age [y:d:h:m:s]: 00:173:21:55:57
Block: 1344350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123425 RingCT/type: yes/0
Extra: 01c5b17fbab5b416c6e1b70be2574ad995bd652770d6f7068cceaa1f3a5f007d9f021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20adeb1159221dadc160fb3c5963ad8a0ac3ec97a87b3a803b780577133ec763 0.600000000000 1832233 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": 1344360, "vin": [ { "gen": { "height": 1344350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20adeb1159221dadc160fb3c5963ad8a0ac3ec97a87b3a803b780577133ec763" } } ], "extra": [ 1, 197, 177, 127, 186, 181, 180, 22, 198, 225, 183, 11, 226, 87, 74, 217, 149, 189, 101, 39, 112, 214, 247, 6, 140, 206, 170, 31, 58, 95, 0, 125, 159, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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