Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48e09aae3a8835b108bc1fb34ea665e752a2a9bef7f52ed9a83de79933f548a8

Tx prefix hash: 05ebe21458ab0913b4dc814d2ea855bcd1de7e2d1f69d293c88bbee649e1b1b4
Tx public key: 6ed601c41a5422c7f7df58b509c5b3d70718ff8d80b150096731b117c969cc07
Timestamp: 1714317302 Timestamp [UCT]: 2024-04-28 15:15:02 Age [y:d:h:m:s]: 00:355:18:10:55
Block: 1010430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254329 RingCT/type: yes/0
Extra: 016ed601c41a5422c7f7df58b509c5b3d70718ff8d80b150096731b117c969cc0702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea22f89a5d672c518d8358418e12bec64406fea035ee82c6ac48c272f0b1ada3 0.600000000000 1472386 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": 1010440, "vin": [ { "gen": { "height": 1010430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea22f89a5d672c518d8358418e12bec64406fea035ee82c6ac48c272f0b1ada3" } } ], "extra": [ 1, 110, 214, 1, 196, 26, 84, 34, 199, 247, 223, 88, 181, 9, 197, 179, 215, 7, 24, 255, 141, 128, 177, 80, 9, 103, 49, 177, 23, 201, 105, 204, 7, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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