Wallet not syncing? Checks for Bitcoin and crypto wallets

Start with the synchronization status

A wallet that stays offline or stops updating needs a different check from a wallet that has finished syncing but shows no balance. First establish which one you are seeing. Do not reset the wallet, delete its data or send another payment to test it.

1. Record what has stopped. Note the wallet name and version, the error message, the latest block or synchronization percentage, and whether those figures change over time.
2. Check the connection. Confirm that the device is online and the wallet has connections to its network or server. Check the provider's official status information where available. Keep the device awake during a long initial sync.
3. Check the device and software. Look for low disk space, a paused app or connection errors. Use updates from the wallet's official website or verified app-store listing. Review firewall, VPN or proxy settings without disabling security protections wholesale.
4. Compare public transaction data. If a payment is missing, check its transaction ID and receiving address on an explorer for the correct network, as explained below.
5. Preserve recovery data before making changes. Follow the wallet's backup instructions before reinstalling, clearing app data or rebuilding a database. A rescan is not a substitute for a backup.

For Bitcoin Core, the official backup facility creates a consistent wallet backup. Do not assume that copying an open database, or saving only the downloaded blockchain, preserves your wallet. If the software cannot open the file, preserve the existing files before attempting repairs.

Check what the backup actually covers: a recovery phrase may not include separately imported private keys. Keep any required passphrase and account or derivation information securely as well.

Why different wallets synchronize differently

Full-node wallets: check progress, storage and peers

Bitcoin Core and Daedalus run a node locally. An initial synchronization can take a long time because the software downloads and validates blockchain data. Recent transactions may be absent until the node reaches the relevant blocks and the wallet has scanned them. An incomplete balance is not a reliable final balance.

Check whether the processed block height advances, whether peers are connected, whether storage is available and whether a wallet scan is still running. Slow progress is different from a fixed error or a process that repeatedly stops at the same point. Record that distinction before asking official support for help.

Do not delete the data directory to make synchronization restart. It can contain wallet files as well as replaceable blockchain data. Reindexing the blockchain and rescanning a wallet are different operations; neither should be the first response to an unexplained delay.

Light wallets and browser wallets: check the data connection

Electrum obtains transaction history from servers rather than downloading the full blockchain. Browser wallets such as MetaMask also depend on network connections to retrieve balances. An unavailable or lagging server can leave the display outdated, but the symptom alone does not establish the cause.

Use the wallet's documented connection settings. Electrum can connect to a different server; its public servers are independently operated, and querying one exposes information about the addresses being checked. For a browser wallet, verify the selected network and use network-provider information from official documentation. Do not import a network configuration supplied by an unsolicited support message.

Check a missing payment on the correct blockchain

Find the transaction ID (TXID) in the sending wallet or platform. An exchange withdrawal reference is not necessarily a blockchain transaction ID. In an explorer for the network actually used, compare:

• The sending and receiving addresses.
• The asset, amount and, for tokens, the relevant token transfer.
• The transaction's execution status and confirmations.
• Any required memo or destination tag.
• The receiving address's current holdings and later outgoing activity, not just an old incoming payment.

An explorer needs only public information. Never enter a recovery phrase, private key or wallet password. Looking up an address also shares it with the explorer, so consider that privacy trade-off.

Confirmed, pending, failed or not found

Confirmed: inclusion in a block does not by itself prove that a smart-contract call succeeded. Check the result and the actual transfer. A successful payment to the intended address establishes what happened then; it does not prove the balance remains there now or that an exchange has credited your account.

Pending: the transaction has not yet been included. Fees, network conditions and earlier pending transactions can matter. On Ethereum, an earlier pending transaction from the same account can hold up later nonce numbers. Use the wallet's documented replacement or speed-up procedure where supported, rather than sending the payment again blindly.

Failed: an Ethereum transaction can be recorded on-chain even though its intended operation reverted, and gas fees can still be charged. Read the failure reason and current state before retrying. A locally rejected or never-broadcast transaction is a different situation.

An out-of-gas error, a contract rejection, an unmet token-approval requirement or an expired swap can require different remedies. Insufficient native currency for the fee can prevent a transaction from being accepted in the first place. Do not grant new token permissions merely because an unfamiliar support site tells you to.

Not found: check the TXID, network and sending platform. The transaction may not have been broadcast, may no longer be known to the explorer, or may be on another network or layer 2. One unsuccessful lookup is not proof that a payment never happened.

When the problem is not synchronization

A token is missing from the display

A token can exist on several networks, and its name or ticker is not a unique identifier. Confirm the network and official contract address through the project's own information. If the expected token balance is present at an address you control and your wallet supports it, adding the token to the display may make it visible. This does not move funds or restore missing keys.

A payment used a different network

The same externally owned address can be controlled by the same private key on multiple EVM networks. That does not mean every matching-looking address is accessible: exchange deposit addresses and smart-contract wallets need separate assessment. Check the actual receiving address, key control, network support and token contract. Sending onward also requires the network's native asset for fees.

A bridge is not needed merely to display a token. It is a separate transfer operation with its own supported assets, costs, minimums and contract risks. Verify those details and control of the receiving address before considering it; a small test does not eliminate those risks. A bridge cannot give you access to an address you do not control. For other network combinations, do not infer recoverability from a familiar address format.

A payment went to another address or an exchange

Synchronizing your wallet cannot reverse a confirmed payment. If you know the recipient, contact them. For an exchange deposit, contact the receiving platform with the TXID, addresses, network, asset, amount, time and any memo or tag. An omitted tag can prevent internal credit even when the on-chain deposit succeeded; the platform decides whether it can identify and credit it, and may charge a fee.

For a contract address, recovery depends on the contract's functions and permissions. Contact the legitimate project or platform; do not assume its developers can retrieve a transfer. An unknown public address does not reveal the private key needed to spend from it.

The wallet was restored but the expected accounts are absent

This needs a separate account-discovery check. A different receiving address alone is not proof of a wrong recovery phrase: an HD wallet can generate many addresses. Compare known transaction history and check the original wallet type, account, derivation settings and any recovery passphrase. A mistyped BIP-39 passphrase derives a different wallet rather than reporting an invalid password.

Use our zero balance after restoration guide and derivation path and account checks for that investigation. If the app will not open at all, start with a Bitcoin wallet that will not open.

Hardware wallets and watch-only wallets

A hardware wallet's companion app retrieves balances from network services; the device holds the signing keys. Check the expected device, account, network and any passphrase-protected account, along with app updates and service availability. A loading error alone says nothing conclusive about the balance. Follow the manufacturer's instructions if clearing the app cache is appropriate; do not reset the hardware device to troubleshoot an ordinary display issue.

A watch-only wallet can synchronize and show transactions without possessing the private keys to sign a payment. Spending requires the original signing wallet, hardware device or appropriate recovery material. An address, xpub or watch-only export cannot be turned back into the private keys.

When to ask for help

Official wallet support is the first contact for a server outage, connection error or supported app configuration. Provide the wallet version, public TXID where relevant and the error text. Check that logs or screenshots contain no recovery secrets before sharing them.

If the investigation instead reveals an inaccessible old wallet, damaged wallet data or an account structure you cannot reproduce, a wallet recovery assessment can establish which access-recovery options remain. Crypto Recovers cannot reverse a confirmed transaction or force an exchange to credit a deposit. Do not send recovery phrases, private keys or passwords through the enquiry form.

If that route restores access, we never hold or move the funds. You transfer them yourself to a new wallet you created, and the agreed fee is paid separately under the contract.

Keep a usable record for next time

Privately record the wallet software and devices used, the networks and accounts, important public addresses, any custom derivation settings and whether a recovery passphrase is required. Store recovery secrets securely offline; a screenshot of a balance is not a backup.

Before a large transfer, check the destination address, network, asset, official token contract and any required memo or tag. A small test can reveal some mistakes before sending the remaining amount, but does not guarantee that every later transfer will succeed.

Frequently asked questions

How long should a wallet take to synchronize?

There is no single time limit. A full node's initial download can take days depending on the device and connection; a light wallet does not download that same history. Check whether progress continues and whether there are errors rather than judging by elapsed time alone.

Does an explorer balance prove I can spend the funds?

No. It shows public blockchain information for that address and network. You still need the correct signing keys and any other spending requirements; a watch-only wallet can display the same balance.

Should I reinstall a wallet that is stuck syncing?

Not as the first step. Check progress, connections and official troubleshooting advice first. Reinstallation or clearing app data can erase local wallet information, so confirm a usable backup and the required recovery details before taking either action.

Must I share my recovery phrase to diagnose synchronization?

No. Connection status, software version, error messages and relevant public transaction data are the starting points. A support agent does not need your recovery phrase or private keys to check a synchronization problem.

Sources

• Bitcoin: running a full node
• Bitcoin Core: managing and backing up wallets
• Electrum: servers and transaction handling
• MetaMask: troubleshooting
• MetaMask: incorrect or missing token balances
• Ethereum: transactions
• XRPL: source and destination tags
• Ethereum: accounts
• Ethereum: bridges and their risks
• Daedalus: official wallet information