Investigate an unexpected balance or transaction
An unexpected balance or pending transaction is a symptom, not proof of a specific bug. Start with non-destructive checks.
- Applies to
- Daedalus 11.0.0 · mainnet
- Platform scope
- Windows, macOS, Linux · OS release compatibility is not established by this guide.
- Sources reviewed
Before you begin
- Use the genuine application and keep private backups private.
Steps
- Check synchronization status and confirm privately that you selected the intended wallet. After restoration, check that the backup belongs to that wallet.
- Inspect transaction details and distinguish sent, received and fee amounts. Treat embedded transaction metadata as untrusted; it can contain misleading links.
- If the result remains unexpected, contact support with the application version and visible status. Avoid repeatedly sending funds or deleting data while the outcome is uncertain.
Expected result
You have a clearer account of the discrepancy. No particular stuck-transaction remedy or recovery outcome is established here.
Consequences and precautions
- Changing or approving wallet operations can affect funds.
If you cannot continue safely
- Stop if unsure; contact human support before changing wallet data.
Keep your wallet safe
- Never disclose recovery phrases, seed words, private keys or spending passwords.
- Do not delete, reset or move wallet data using generic instructions.
When to contact support
- The symptom persists after the safe diagnostic steps, or funds appear at risk.
Sources and review
Official source inspection and Ariadne safety review; not wallet runtime testing.
These are editorial summaries of the cited sources. Review dates describe source checks, not installation or wallet testing. Historical screenshots are not used as current instructions.
- 11.0.0 restoration result guidance — Input Output. Accessed 2026-09-22.
- 11.0.0 transaction detail fields — Input Output. Accessed 2026-09-22.
- 11.0.0 diagnostics fields — Input Output. Accessed 2026-09-22.