Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eaf17451dfb219f52f5e59cabef7784ed0faffeed56840897b45d17ed174e70

Tx prefix hash: 9b77a75d50569b6f4e1b00dcc26b3b5066db91888ef9aa3e73daf697cbc38bf5
Tx public key: 7411c458868b7dbf2e1e0678de900b8b5138b1aa9f34e2a59888d2cf672d4799
Timestamp: 1719016327 Timestamp [UCT]: 2024-06-22 00:32:07 Age [y:d:h:m:s]: 00:270:10:38:50
Block: 1049389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193277 RingCT/type: yes/0
Extra: 017411c458868b7dbf2e1e0678de900b8b5138b1aa9f34e2a59888d2cf672d47990211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1949b5d2437de04f49e6c7e31d614993f6070865f4ef7ce8dd2a9dfc901f6828 0.600000000000 1519488 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": 1049399, "vin": [ { "gen": { "height": 1049389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1949b5d2437de04f49e6c7e31d614993f6070865f4ef7ce8dd2a9dfc901f6828" } } ], "extra": [ 1, 116, 17, 196, 88, 134, 139, 125, 191, 46, 30, 6, 120, 222, 144, 11, 139, 81, 56, 177, 170, 159, 52, 226, 165, 152, 136, 210, 207, 103, 45, 71, 153, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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