Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c935a75b963395d347b9161ee5e5cdc9b77366a2dd94d790775df92b7038142

Tx prefix hash: 562c84982ca68e618aca84ad8b706cb49f41e015effdc591e81d143da56af8dd
Tx public key: a571d6c19cf2725f14708a7ccb5db6b7c69ed1f7157ec5a411e8073645cc95c3
Timestamp: 1750862471 Timestamp [UCT]: 2025-06-25 14:41:11 Age [y:d:h:m:s]: 00:146:12:14:52
Block: 1312578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102659 RingCT/type: yes/0
Extra: 01a571d6c19cf2725f14708a7ccb5db6b7c69ed1f7157ec5a411e8073645cc95c3021100000016bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4db9a2fda3f5a216308319dff9bbb87451032d5e32b49ab6fdc2c047fb870bcd 0.600000000000 1800211 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": 1312588, "vin": [ { "gen": { "height": 1312578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4db9a2fda3f5a216308319dff9bbb87451032d5e32b49ab6fdc2c047fb870bcd" } } ], "extra": [ 1, 165, 113, 214, 193, 156, 242, 114, 95, 20, 112, 138, 124, 203, 93, 182, 183, 198, 158, 209, 247, 21, 126, 197, 164, 17, 232, 7, 54, 69, 204, 149, 195, 2, 17, 0, 0, 0, 22, 191, 81, 178, 162, 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