Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 824ac7dd63f2d162258f860e3a7fd46d395d328d0c0246bd60244d5bcb2c23db

Tx prefix hash: 2bcc57eecf06907d43de7c69cdac0e94b65943f5e80f968ede4887dcdd1955eb
Tx public key: 9e32ae816f5d700bcb1cc5719b74300c341090bd7f37db429df4876838c81c83
Timestamp: 1713489813 Timestamp [UCT]: 2024-04-19 01:23:33 Age [y:d:h:m:s]: 01:200:04:05:43
Block: 1003574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401704 RingCT/type: yes/0
Extra: 019e32ae816f5d700bcb1cc5719b74300c341090bd7f37db429df4876838c81c83021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51cf44fb88835d60a9d5b5e412b77fce706d064ba90aebbb21d7cfad904b78c2 0.600000000000 1464116 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": 1003584, "vin": [ { "gen": { "height": 1003574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51cf44fb88835d60a9d5b5e412b77fce706d064ba90aebbb21d7cfad904b78c2" } } ], "extra": [ 1, 158, 50, 174, 129, 111, 93, 112, 11, 203, 28, 197, 113, 155, 116, 48, 12, 52, 16, 144, 189, 127, 55, 219, 66, 157, 244, 135, 104, 56, 200, 28, 131, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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