> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/features/managing-your-wallet/rescan.md).

# Rescan

How to rescan your wallet in Cake Wallet when transactions are missing: open Settings, Connections, pick a restore date or block height, and let history reload.

{% hint style="warning" %}
Rescanning will remove any saved transaction keys and destination addresses, which may be useful for proving payments.

If your XMR transaction is still not appearing and the wallet has already finished syncing, then you can rescan by opening `Settings` in the top-right, tapping `Connections`, then tapping `Rescan`.
{% endhint %}

{% stepper %}
{% step %}

### Open the rescan controls

Open `Settings` from the top-right, tap `Connections`, then tap the `Rescan` button.

The `Rescan` button under `Connections` is shown for Monero, Zcash and Decred wallets.

![Open Settings, tap Connections, then tap Rescan](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/settings_rescan_01_connections_hl.png)
{% endstep %}

{% step %}

### Choose a restore date or block height

![Enter a restore date or block height, then tap Rescan](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/settings_rescan_02_dialog_hl.png)

For Monero and Zcash wallets, Cake Wallet fills in the block height with the restore height saved for this wallet, which is usually the right starting point — only change it if you know your first transaction is older. Otherwise, enter a date or a block height from about a week before you created this wallet. For example, if the wallet was created in February 2020 you could use January 31st, 2020 as the "restore from date." Alternatively, use the "Height" shown for your wallet's very first transaction and enter that number as the "Block height."

After entering the date and tapping Rescan, leave the Cake Wallet app open with your phone awake while the wallet rescans the blocks for transactions involving your wallet. When the rescan starts, your transaction history will disappear and your balance will read as 0.0 XMR. As the wallet continues scanning blocks, your transaction history will reappear one transaction at a time. When the rescan is completed, the sync progress status and indicator at the top of the balance screen will disappear and your entire transaction history and proper balance will be restored.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cakewallet.com/features/managing-your-wallet/rescan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.