Cannot withdraw transparent balance


I have a balance that says “Transparent balance”. When I view that address it says “if the balance of an address is flagged as not confirmed, the address is currently taking part in a transaction.” This transaction dates back to Feb. 13, 2018, so something must be wrong. Here’s the address:


Can you help me get my ZenCash?



The address znSqXBidFoqBLgX9v47sWe2CPLCo2hsvxoJ as seen in the block explorer:
has two transactions. Both are confirmed and are of today’s date (Jun 4, 2018). The balance is 2.9968 zen.

Does the ZENCash Desktop GUI Wallet show a different balance for the address? or show the balance as unconfirmed? Is the block-chain 100% synchronized in the GUI?


You were correct to ask about whether or not the block-chain is 100% synchronized…it is not. It’s going along very slowly but I shall wait until that completes and then write to you again. The balance of 2.9968 is not part of the “Private (Z) balance”. That reads as zero “0”. It’s part of the “Transparent Balance”.




Hi. Apparently I’m having trouble syncing to the BlockChain. I would like to move those tokens off of this wallet permanently, asap. Any advice on what to do next?


The wallet problem (GUI error) may be happening because the wallet is not the latest version, or for other reasons… Before proceeding it is a good idea to make sure your wallet.dat file is backed up.

The ZEN private keys are located in the wallet.dat file in directory:
Windows: %APPDATA%/Zen/
Mac OS: ~/Library/Application Support/Zen/

It is critically important to keep a backup copy of the wallet.dat file - it must never be lost! It may be copied manually when the GUI wallet/zend are not running. The wallet.dat needs to be backed up regularly (not just once - say after every few outgoing transactions) and it MUST also be backed up after creating a new Z address.

Once a wallet backup is available, if the version is too old it needs to be updated:
If the problem persists there is a procedure to reindex the blockchain that often helps:


The appropriate document for this issue is now at: