Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a12a32b36e9d37e5a81fd3df04e6323db40cd9213bdaee3da3e0b291e17dd70c

Tx prefix hash: c360b3616d683e22f61b21dc5f3148de39220d1f4c0efa4029ad7af4755c096f
Tx public key: 79b8be9b76c2c4f6c76fccf1275d6697ebb304dc5955e2f3fab2125723192b07
Timestamp: 1745403876 Timestamp [UCT]: 2025-04-23 10:24:36 Age [y:d:h:m:s]: 00:279:10:54:05
Block: 1267651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197365 RingCT/type: yes/0
Extra: 0179b8be9b76c2c4f6c76fccf1275d6697ebb304dc5955e2f3fab2125723192b07021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 020165826d9168a591460239934216e760595ecb4e32ae4b33a58039e339e89b 0.600000000000 1754880 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": 1267661, "vin": [ { "gen": { "height": 1267651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "020165826d9168a591460239934216e760595ecb4e32ae4b33a58039e339e89b" } } ], "extra": [ 1, 121, 184, 190, 155, 118, 194, 196, 246, 199, 111, 204, 241, 39, 93, 102, 151, 235, 179, 4, 220, 89, 85, 226, 243, 250, 178, 18, 87, 35, 25, 43, 7, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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