Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 872171f865272d380e8e65bd0f65fe75868928ea87b3d3b228a290321463d558

Tx prefix hash: d735afdce4bff19d00add3db3d7ab2efe98b11452573e72a8571febbf37c3d2c
Tx public key: 307cf9836fdff03fe64252b93b28b096df9e1d68d0f31eb2f680c5d8373fd3e1
Timestamp: 1703918042 Timestamp [UCT]: 2023-12-30 06:34:02 Age [y:d:h:m:s]: 01:325:08:06:27
Block: 924228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491357 RingCT/type: yes/0
Extra: 01307cf9836fdff03fe64252b93b28b096df9e1d68d0f31eb2f680c5d8373fd3e10211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8001c41772012da871fa6c296f215a7c799eeeb031bc1aa092e14725ed9e796e 0.600000000000 1381972 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": 924238, "vin": [ { "gen": { "height": 924228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8001c41772012da871fa6c296f215a7c799eeeb031bc1aa092e14725ed9e796e" } } ], "extra": [ 1, 48, 124, 249, 131, 111, 223, 240, 63, 230, 66, 82, 185, 59, 40, 176, 150, 223, 158, 29, 104, 208, 243, 30, 178, 246, 128, 197, 216, 55, 63, 211, 225, 2, 17, 0, 0, 0, 5, 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