Skip to article
Degrees of SatoshiFollow the connections.
Degrees of Satoshi/ Encyclopedia

Encyclopedia Bitcoin basics · Entry 180

Bitcoin received but missing from your wallet: what to check

Theme
Bitcoin basics
Sources
12 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for Bitcoin received but missing from your wallet: what to check
FactDetailSource
First comparisonExact destination and network[5][2]
DiscoveryAn address gap can hide later used addresses[3][6]
AuthoritySeeing an output is different from signing it[1]
01

Establish which payment is missing

Inspect the recipient output, not just the transaction’s total. Confirm you are viewing the expected network and account. A wallet can display pending, trusted, immature or watch-only balances separately, so one screen may not equal all value associated with its addresses.

Suppose an explorer shows 40,000 satoshis to the expected script at a recorded block. That proves a historical receipt in that chain view, not that the output is still unspent or that your current application can authorize it.

02

Compare chain progress before changing recovery data

A local node still processing older blocks may not have reached the payment. Core exposes block height, header height and an estimated verification progress. A wallet rescan searches available local blocks for relevant transactions; it does not recreate a missing key.

Check the wallet’s documented rescan and synchronization procedure. On a pruned node, old block bodies may need to be obtained again before a historical scan can succeed.

03

Check account derivation and the discovery window

A correct-looking mnemonic can still be used with the wrong passphrase, derivation path, address type or account. BIP-39 normalizes its mnemonic and passphrase before deriving a seed; a different normalized passphrase gives another wallet rather than a useful wrong-wallet warning.

BIP-44 discovery stops after a defined unused-address gap. A later used address can be missed if addresses were generated outside the normal discovery pattern. Investigate with the wallet’s documented settings and known public addresses, not by uploading recovery secrets.

Direct answers

Questions people ask

Does a zero balance after recovery mean the bitcoin is gone?

No. An incorrect account, derivation convention, normalized passphrase or incomplete address search can show a different or incomplete wallet. Compare known receiving addresses and transaction records before reaching that conclusion.

Will a blockchain rescan recover a lost seed?

No. Rescanning finds transactions relevant to key or script information already available to the wallet. It cannot derive missing spending secrets from the public chain.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

A confirmed Bitcoin payment missing from a wallet display can be a discovery or synchronization problem rather than a lost payment. First match the network, destination and amount; then check the wallet’s chain progress, account and recovery settings. A visible public output does not establish that the open wallet holds its spending keys. Do not share a seed with an explorer or support stranger.

Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
First comparison: Exact destination and network

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Discovery: An address gap can hide later used addresses

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Authority: Seeing an output is different from signing it

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

On the Send and check a Bitcoin payment path · Learn next: Bitcoin refunds: why returning a payment requires a new transaction

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. WalletsBitcoin developer documentation

    Wallet types, generated keys, deterministic wallets and offline signing.

    Locator: Wallet Programs; Full-Service Wallets; Signing-Only Wallets; Wallet Files; Hierarchical Deterministic Key Creation; Loose-Key Wallets · Version / scope: Developer guide; historical implementation details require qualification · Retrieved: 2026-10-02T18:53:53.756ZOpen source
  2. getblockchaininfo RPCBitcoin Core

    Network identity and sync-status fields; progress is an estimate.

    Locator: Result: chain, blocks, headers, verificationprogress, initialblockdownload · Version / scope: Bitcoin Core 29.0 RPC reference; not a recommendation to install an old release · Retrieved: 2026-10-02T18:53:55.851ZOpen source
  3. Frequently Asked QuestionsElectrum

    Electrum-specific sweep/import distinctions, seed recovery scope and address discovery.

    Locator: Does Electrum trust servers?; Can I import private keys from other Bitcoin clients?; Can I sweep private keys from other Bitcoin clients?; What is the gap limit?; How do I upgrade Electrum? · Retrieved: 2026-10-02T18:53:56.378ZOpen source
  4. Securing your walletBitcoin.org

    Backup scope, online exposure, offline signing, custody and software update practices.

    Locator: Be careful with online services; Backup your wallet; Encrypt your wallet; Offline wallet for savings; Hardware wallets; Keep your software up to date · Retrieved: 2026-10-02T18:53:53.659ZOpen source
  5. TransactionsBitcoin developer documentation

    Inputs, outputs, authorization, change, coinbase exceptions and fee accounting.

    Locator: Introduction; Spending An Output; P2PKH Script Validation; Multisig; Transaction Fees And Change; Avoiding Key Reuse · Version / scope: Developer guide; historical implementation details require qualification · Retrieved: 2026-10-02T18:53:53.759ZOpen source
  6. Multi-Account Hierarchy for Deterministic WalletsBitcoin Improvement Proposals

    Hardened account paths and external-chain discovery gap rule.

    Locator: Path levels; Account discovery; Address gap limit · Version / scope: Pinned BIPs revision · Retrieved: 2026-10-02T18:53:54.097ZOpen source
  7. getbalances RPCBitcoin Core

    Wallet balances are divided by trust and spendability-related categories.

    Locator: Result: mine, watchonly, trusted, untrusted_pending, immature · Version / scope: Bitcoin Core 29.0 RPC reference; not a recommendation to install an old release · Retrieved: 2026-10-02T18:53:55.000ZOpen source
  8. rescanblockchain RPCBitcoin Core

    Rescan local blocks for wallet-related transactions within a height range.

    Locator: Description; Arguments; Result · Version / scope: Bitcoin Core 29.0 RPC reference; not a recommendation to install an old release · Retrieved: 2026-10-02T18:53:55.698ZOpen source
  9. Node initializationBitcoin Core

    Definitions of reindex/chainstate rebuild and node configuration switches.

    Locator: SetupServerArgs: assumevalid, reindex, reindex-chainstate, prune, listen, server; prune/reindex-chainstate compatibility check · Version / scope: Bitcoin Core v29.0 · Retrieved: 2026-10-02T18:53:55.958ZOpen source
  10. FilesBitcoin Core

    Wallet, block, chainstate and index files have different recovery purposes.

    Locator: Data directory location and chain-specific paths; Data directory layout: blocks/, chainstate/, wallets/; Multi-wallet environment and backupwallet guidance · Version / scope: Bitcoin Core v29.0 · Retrieved: 2026-10-02T18:53:55.926ZOpen source
  11. Hierarchical Deterministic WalletsBitcoin Improvement Proposals

    Deterministic key derivation, backup scope and public/private child derivation.

    Locator: Motivation; Extended keys; Security · Version / scope: Pinned BIPs revision · Retrieved: 2026-10-02T18:53:54.013ZOpen source
  12. Mnemonic code for generating deterministic keysBitcoin Improvement Proposals

    Entropy and checksum table, intended computer-generated randomness and NFKD seed derivation.

    Locator: Generating the mnemonic; From mnemonic to seed · Version / scope: Pinned BIPs revision · Retrieved: 2026-10-02T18:53:54.120ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

Degrees of Satoshi editorial project. “Bitcoin received but missing from your wallet: what to check.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-payment-not-showing-in-wallet/