Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9999a2d571159969edd6abbabf5deac8aecfc05b33dc55232207746d66a963f

Tx prefix hash: 1145da87f524e17eae328ab071c582827be455ed803a285c5dd929f6df698e50
Tx public key: 5d5dfda665bb3fbf6447136a1204210ad3e911ef8ab7bba06245f396db2c0a42
Timestamp: 1752397810 Timestamp [UCT]: 2025-07-13 09:10:10 Age [y:d:h:m:s]: 00:137:21:12:20
Block: 1324502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97284 RingCT/type: yes/0
Extra: 015d5dfda665bb3fbf6447136a1204210ad3e911ef8ab7bba06245f396db2c0a4202110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f8b83f250bbbf56d8a9bc5ff4f8c5e5e446a68fdab1b35fa87aae68b44cb81 0.600000000000 1812245 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": 1324512, "vin": [ { "gen": { "height": 1324502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f8b83f250bbbf56d8a9bc5ff4f8c5e5e446a68fdab1b35fa87aae68b44cb81" } } ], "extra": [ 1, 93, 93, 253, 166, 101, 187, 63, 191, 100, 71, 19, 106, 18, 4, 33, 10, 211, 233, 17, 239, 138, 183, 187, 160, 98, 69, 243, 150, 219, 44, 10, 66, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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