How to sync a Monero wallet
A Monero wallet synchronizes by scanning blockchain data for outputs belonging to its keys. This is how it discovers payments; installing the application or connecting to a node alone does not finish that scan.
Quick Answer
Open your Monero wallet, connect to a working synchronized node and leave the app running until scanning reaches the current chain height. For restored wallets, use a restore height or date at or before the first transaction. Check connection, disk space and progress if scanning stops; never delete secret wallet files as a first troubleshooting step.
Run the normal synchronization process
In Best Wallet, select a suitable remote node or your own node, open the intended wallet and allow its scan to complete. A remote node avoids downloading a full blockchain database locally, but the wallet still needs to scan the relevant data.
- Confirm you opened the correct wallet.
- Check the node connection and that the node is on the current network.
- Allow scanning to advance without closing or suspending the app.
- Check the wallet height and synchronization status.
- After syncing, wait for any required output confirmations before spending.
Set a safe restore height
A restored wallet has to rediscover its history. A restore height starts scanning at a particular block; setting it after an old payment can hide that payment from the wallet's scan. Choose a height at or before your first relevant transaction.
If you do not know the date, a more conservative earlier height increases scan time but avoids skipping payments. Changing the height or rescanning is not the same as creating new keys. Keep the recovery backup safe before making recovery changes.
If the scan stops or is slow
Check connectivity, node health, disk space, app version and device sleep settings. Trying a different trusted node may help identify whether the connection is the problem. Tor configuration can affect connectivity and speed; use the documented mode rather than assuming every route is available.
If progress continues, a slow initial scan may simply need time. If it stalls, use the existing stuck-sync troubleshooting guidance before rebuilding caches. Do not remove key files or disclose a seed to someone promising instant synchronization.
Synchronization and confirmation are different
Scanning discovers transactions; network confirmations determine whether newly received outputs are spendable. A wallet can be fully scanned while some funds remain locked pending the necessary confirmations.
An incoming balance that differs before synchronization is complete is not a reliable final balance. Compare the sending transaction details and wallet history after the scan rather than repeating a transfer immediately.
Sources
Related reading
Key takeaways
- A connected node does not mean scanning is finished.
- Use a restore height early enough to include all payments.
- Protect key files before any rescan or cache repair.
