Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e742fa3f3127a6f53a06bd39d1585e4661c5d4c6017b4e85a7cefddd3459c498

Tx prefix hash: e38eafad111b2812b5129fdebcc99b639fb2755f489d08f12575dfce13faa956
Tx public key: 842668c8ffe2e170fb6d3d0ebcdf48bcb61e987cb24eba3fa2e423bc0f8e1feb
Timestamp: 1718692067 Timestamp [UCT]: 2024-06-18 06:27:47 Age [y:d:h:m:s]: 00:189:07:29:47
Block: 1046714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135493 RingCT/type: yes/0
Extra: 01842668c8ffe2e170fb6d3d0ebcdf48bcb61e987cb24eba3fa2e423bc0f8e1feb0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ca35d6184af798db0b062813c98c037844193851c8e6d4d0e57618fa1da7de1 0.600000000000 1516533 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": 1046724, "vin": [ { "gen": { "height": 1046714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ca35d6184af798db0b062813c98c037844193851c8e6d4d0e57618fa1da7de1" } } ], "extra": [ 1, 132, 38, 104, 200, 255, 226, 225, 112, 251, 109, 61, 14, 188, 223, 72, 188, 182, 30, 152, 124, 178, 78, 186, 63, 162, 228, 35, 188, 15, 142, 31, 235, 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