Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d7e570c9968e6bea128d0c47dd10c05ae247dce5afdbf749c8ea3ed127438a

Tx prefix hash: 4e0fc585e8daf6f8c6a8792c411453ac04850e4b3f6c5bc55cef73ffeb3fd6ff
Tx public key: e9050f4c19c0c41683e6c8fcdffe5e2b9ec823cbddff65e1d9598d9dcf2ee55d
Timestamp: 1752740972 Timestamp [UCT]: 2025-07-17 08:29:32 Age [y:d:h:m:s]: 00:119:21:34:23
Block: 1327289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84464 RingCT/type: yes/0
Extra: 01e9050f4c19c0c41683e6c8fcdffe5e2b9ec823cbddff65e1d9598d9dcf2ee55d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7ba29be93510e5161bee961eab8b17f18b8cb4dde6fbcebf04f61ba29613932 0.600000000000 1815042 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": 1327299, "vin": [ { "gen": { "height": 1327289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7ba29be93510e5161bee961eab8b17f18b8cb4dde6fbcebf04f61ba29613932" } } ], "extra": [ 1, 233, 5, 15, 76, 25, 192, 196, 22, 131, 230, 200, 252, 223, 254, 94, 43, 158, 200, 35, 203, 221, 255, 101, 225, 217, 89, 141, 157, 207, 46, 229, 93, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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