Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c765bcf935850c498387bdb3507e639d4543ac951cbc5a3ad26d40ba71eccb36

Tx prefix hash: b813c3a1ea2d4d3e091bb3494df82f455e500ca4efc97d83ca4d2ddea459e957
Tx public key: 6e34e5810bb919f49cf84d8ff7d990b192174f2e05165f947fe7cc48b29dc7bd
Timestamp: 1727077943 Timestamp [UCT]: 2024-09-23 07:52:23 Age [y:d:h:m:s]: 00:265:04:48:13
Block: 1116239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189295 RingCT/type: yes/0
Extra: 016e34e5810bb919f49cf84d8ff7d990b192174f2e05165f947fe7cc48b29dc7bd02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9e1f8258dc9697ad0736182374511480d4bdc02e4fb76abfebd3e780e848bb3 0.600000000000 1596650 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": 1116249, "vin": [ { "gen": { "height": 1116239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9e1f8258dc9697ad0736182374511480d4bdc02e4fb76abfebd3e780e848bb3" } } ], "extra": [ 1, 110, 52, 229, 129, 11, 185, 25, 244, 156, 248, 77, 143, 247, 217, 144, 177, 146, 23, 79, 46, 5, 22, 95, 148, 127, 231, 204, 72, 178, 157, 199, 189, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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