I withdrew from Kraken / Poloniex / Bitfinex / Poloniex / any other exchange or service (e.g. Shapeshift) and I am not seeing the transaction in the GUI. How do I resolve this issue?

  • Mine will not fully sync and under “show status” says “error could not connect to daemon” – Daniel Carr Dec 6 '17 at 2:09
  • Which operating system? – dEBRUYNE Dec 6 '17 at 10:14
up vote 19 down vote accepted

First and foremost, to put your mind and ease and to verify that your transaction was correctly sent to your address, use this guide to verify your transaction:

How do I, as a recipient, verify that my transaction actually arrived?

It should show that you have one output with output match? = True for the amount you expect to receive. If this checks out, you can proceed with the rest of the guide.


It's important to make sure you're running the latest version (v0.12.0.0 at the time of writing). You can check the version # on the Settings page of the GUI (under Debug info). If you're not running v0.12.0.0, please upgrade first:

How do I upgrade my software to v0.12.0.0?


The following assumes you're using a local node

First, you can check whether you are using a local node by going to the Settings page and looking at the daemon address. It should state localhost (or 127.0.0.1) with port 18081.

Now, the most common "problem" is that people are not fully synced yet or their GUI wallet is erroneously stating that it's fully synced. If you're not fully synced yet, the GUI will not be able to "see" your transaction. To confirm your fully synced, perform these steps:

[1] Go to the Settings page of the GUI.

[2] Press Show status. A window will popup with an output. The output looks like:

Height: 1456425/1456425 (100.0%) on mainnet, not mining, net hash 290.20 MH/s, v6, up to date, x(out)+x(in) connections, uptime xd xh xm xs
Height: 1456428/1456428 (100.0%) on mainnet, not mining, net hash 289.91 MH/s, v6, up to date, x(out)+x(in) connections, uptime xd xh xm xs
Height: 1456429/1456429 (100.0%) on mainnet, not mining, net hash 291.20 MH/s, v6, up to date, x(out)+x(in) connections, uptime xd xh xm xs
Height: 1456444/1456444 (100.0%) on mainnet, not mining, net hash 290.77 MH/s, v6, up to date, x(out)+x(in) connections, uptime xd xh xm xs

Where x is simply an integer. For example, you could have 8 outgoing connections and 2 incoming connections. The Height can be explained as follows. The first number is the height you (personally) are currently on, whereas the second number is the top height (most recent block on the blockchain). The first number can be lower than the second number if you haven't completed the initial sync yet.

[3] Now to verify that you're actually fully synced, compare the first number to the height displayed on a blockchain explorer like, for instance, XMRchain. You're fully synced if your height matches the height displayed on a block explorer.

[4] If the GUI is stating that you're fully synced (100.0%), but your height doesn't match the height displayed on a block explorer (and is off by a large number), it is erroneously reporting that you're fully synced. This is, fortunately, easily resolved as follows. First, exit the GUI and make sure to stop the daemon as well. Second, restart the GUI + daemon. Third, use Show status to verify that it's now correctly displaying the top height.

[5] If the GUI is correctly stating the top block height, but is stuck on a particular block, perform these steps. First, exit the GUI and make sure to stop the daemon as well. Second, restart the GUI + daemon. Third, use Show status to verify that it's now syncing past the block it was stuck on.

[6] On the 6th of April (block 1546000) a scheduled network upgrade occurred, which resulted in a correct chain (Monero) and a wrong (alternative) chain (Monero Classic). Therefore, it could be that you (accidentally) synced to the wrong (alternative) chain. A simple heuristic to verify that you're on the correct chain is to look at the hashrate (net hash in the Show status output). If it's greater than 600 MH/s, you can reasonably assume that you're on the wrong (alternative) chain. In addition, if you upgraded from GUI v0.11 to GUI v0.12 after April 6, you can also reasonably assume that you're on the wrong (alternative) chain. Intuitively, the GUI will not be able to see a transaction sent to your wallet if it's on the wrong (alternative) chain. You can resolve this by following this guide.

Note that after the daemon is fully synced, the wallet will start refreshing. In addition, in Monero, there's two "syncs". First, the blockchain sync, which is basically downloading the blockchain from other nodes / peers. Second, the wallet sync, which is the wallet "refreshing" / scanning blocks looking for transactions belonging to your address / wallet. Unfortunately, the GUI currently uses the status bar to display both syncs, which can be a bit confusing for newcomers. Thus, if you see the "blocks remaining" starting all over again, don't worry since it's, most likely, the wallet refreshing. Once it finishes, the GUI will state Connected in the left bottom and you should see your funds.

Now, if you're fully synced, the wallet fully refreshed and you don't see your funds yet, perform these steps:

  1. Exit the GUI, but keep the daemon running.

  2. Browse to the directory your wallet files are located (Documents\Monero on Windows | ~/Monero on Linux and Mac OS X).

  3. Rename <wallet-name> (the file without extension) to <wallet-name>-old.

  4. Restart the GUI. This will trigger a wallet refresh from scratch, which shouldn't take longer than 30 minutes.

  5. Once it states Connected (in the left bottom) you should see your funds.

Still not seeing your funds? It might be that a small part of your blockchain is corrupted and it's, coincidentally, the part that contained your transaction. Perform these steps:

  1. Go to the Settings page of the GUI and change localhost to node.moneroworld.com and 18081 to 18089.

  2. Exit the GUI.

  3. Again browse to the directory your wallet files are located (Documents\Monero on Windows | ~/Monero on Linux and Mac OS X).

  4. Rename <wallet-name> (the file without extension) to <wallet-name>-old2.

  5. Restart the GUI. This will trigger a wallet refresh from scratch, which shouldn't take longer than 30 minutes.

  6. Once it states Connected (in the left bottom) you should see your funds.


The following assumes you're using a remote node

If you're using a remote node, you're basically using someone else's public node / blockchain. Therefore, it's unlikely that an uncompleted sync is the issue. Thus, perform these steps:

  1. Exit the GUI, but keep the daemon running.

  2. Browse to the directory your wallet files are located (Documents\Monero on Windows | ~/Monero on Linux and Mac OS X).

  3. Rename <wallet-name> (the file without extension) to <wallet-name>-old.

  4. Restart the GUI. This will trigger a wallet refresh from scratch, which shouldn't take longer than 30 minutes.

  5. Once it states Connected (in the left bottom) you should see your funds.


If you, after all these steps, still don't see your funds (but verified with this guide that they were correctly sent to your address), it'd be best to either open a new issue the GUI repository or contact me on Reddit.

  • I followed this guide and managed to see my balance in the Monero GUI after changing the localhost to node.moneroworld.com (as well as the port) - thanks for the guide. Can you please clarify, after this is done and I see my balance ok, should I leave my daemon pointing to node.moneroworld.com from here on, or should I switch it (and port) back to the default localhost? Thanks! – Katsikas Mar 5 at 18:15
  • Was your daemon fully synced before you switched to the remote node? – dEBRUYNE Mar 5 at 19:41

protected by Community Mar 5 at 23:30

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.