Find the internal data files (related: ‘How do I move the consensus database or internal data files?’), and fully close SiaPrime-UI. Delete the ‘transactionpool’ folder, and reopen SiaPrime. If error persists, repeat these steps and delete the ‘consensus’ folder as well.
This issue typically means the client is not synchronized (though the wallet may think it is – do not always trust it). Perform step 1 from article ‘I can’t see SCP I sent or was sent.’ If not synchronized, see article ‘My wallet is stuck on block 7269 (or any other not up-to-date block height)’ to resolve. If synchronized, wait for an additional block or two to be mined (this should settle outstanding transactions) and try again. If issue persists, perform the resynchronization step above.
SiaPrime is resource intensive while synchronizing consensus, and can cause stutters while this is being performed. SiaPrime is particularly RAM intensive, even when not synchronizing.
There was a hard-fork at block 7200 (12/19/2018) and the other chain continued to height 7269. To resolve, a full consensus resynchronization is required. Fully close the SiaPrime-UI wallet, then find and delete ‘consensus.db’ from the internal data files (see FAQ ‘How do I move the consensus database or internal data files?’ to find). After resynchronizing your consensus should be up to date.
After updating, the UI may need to make significant changes before it is ready for use. This process will be faster on an SSD, and can take up to several hours on a HDD.
Perform these 3 steps first
1) Check your SiaPrime version in the ‘About’ tab of the UI. The ‘SiaPrime UI version’ should match the ‘SiaPrime version’, and both should be the latest version which you can check on https://siaprime.net/#download. Additionally, confirm your wallet is synchronized by running the command ‘consensus’ in the ‘Terminal’ tab and ensuring ‘Height’ matches the most recent block on https://siaprimestats.info/navigator.
2) Double check the correct address. If this is the problem and you were sending to an exchange, contact the exchange. There’s a slim chance they may be able to recover the funds, particularly if the address accidentally sent to was an old exchange one. Otherwise, the coins are unfortunately most likely irretrievable.
3) Use the transaction id (txid) in a block explorer, such as https://siaprimestats.info/navigator. If no transaction is found, then the block containing the transaction has not yet been mined; wait until the next block is mined. If the transaction has been found, then it has been finalized on the network. If sending from an exchange that does not provide the txid, contact them.
Sending to an exchange
As long as the transaction shows up in the block explorer (and transaction reads confirmed in the UI wallet) then the exchange has received the coins, and will often require 6 confirmations (approx. 60 minutes) to become usable. If it does not show up, contact the exchange for support.
Receiving to your SiaPrime wallet
If your wallet is synchronized and transaction is not showing, then try a force rescan.
0.088 transactions indicate wallet defragmentation. The SiaPrime wallet is composed of multiple addresses and moves balances to defragment, causing a transaction on the blockchain. The 0.088 SCP transaction is the network fee for this transaction.
If the address you entered was correct, you should open a support ticket with the exchange after a reasonable period of time. Check the transaction ID in https://siaprimestats.info/navigator to verify.