Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac302ba6a0ab257d76704fefc51eff84a02215e7469cbc5da9016f39c5f0a120

Tx prefix hash: 79857110d2149e57b015d38a57c1ea1107389f6e8090c0ce572a1ca276a9cfa0
Tx public key: 54086ca00b92d0a7e86ae4b92192d09a398f3f0b9aac11222e5d4fa77fb6b562
Timestamp: 1718292305 Timestamp [UCT]: 2024-06-13 15:25:05 Age [y:d:h:m:s]: 00:225:09:55:00
Block: 1043403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161268 RingCT/type: yes/0
Extra: 0154086ca00b92d0a7e86ae4b92192d09a398f3f0b9aac11222e5d4fa77fb6b5620211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec23dca25b7f66fab4470b34cda8487b8e58500a51fb3c6a7793951094f06a9c 0.600000000000 1512548 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": 1043413, "vin": [ { "gen": { "height": 1043403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec23dca25b7f66fab4470b34cda8487b8e58500a51fb3c6a7793951094f06a9c" } } ], "extra": [ 1, 84, 8, 108, 160, 11, 146, 208, 167, 232, 106, 228, 185, 33, 146, 208, 154, 57, 143, 63, 11, 154, 172, 17, 34, 46, 93, 79, 167, 127, 182, 181, 98, 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