Why is my Monero wallet not detecting an old transaction?
Missing historical transactions are frequently caused by an incorrect restore height used during the wallet creation or import process.
Quick Answer
When a wallet fails to detect an old transaction, it is usually because the block scan started after the transaction occurred. Verify that your wallet's restore height matches the approximate block height of your first transaction. If you are unsure, you can re-import the wallet using a lower, safer block height to ensure a comprehensive scan of your entire history.
Correcting the Restore Height
The restore height indicates the blockchain point where the wallet should begin scanning. If this value is higher than the transaction's block height, the wallet will skip over the transaction, making it invisible to the user.
Performing a Full Scan
If you cannot determine the exact restore height, you can set it to a date or block height before you generated the wallet. This triggers a full re-scan and will correctly identify all historical transactions.
Managing XMR with Best Wallet
Best Wallet keeps receiving addresses, sending, history, and transaction-review controls together in a clear desktop interface. Its confirmation workflow lets you check the destination and fee before broadcast, which is useful for avoiding preventable mistakes. Wait for synchronization when checking activity, and remember that an approved Monero transfer cannot simply be reversed.
Explore Best Wallet transaction controlsSources
Related reading
Key takeaways
- Set your restore height before the date of your earliest transaction.
- Use block explorers to identify the approximate block height of your first transaction.
- Re-import the wallet with a lower height to ensure a complete history index.
