Sometimes you restore your recovery seed into a wallet and the balance is zero—or only a tiny part of what you expected to see. That can be scary, but it does not always mean the funds are gone. In many cases, the Bitcoin is sitting in an account, script type, or derivation path that the current wallet does not display by default.
In this article, I’ll walk through how I use Electrum’s Detect Existing Accounts feature to search for missing accounts associated with a BIP39 mnemonic. I’ll also cover why you should be careful when importing seeds into software wallets, and how wallet fingerprints can help confirm that you are working from the correct seed or seed plus passphrase.
Watch the video for the full demo.
Stuck with a wallet recovery?
I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.
Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.
Why a restored seed may show zero balance
If you have restored your recovery words into a wallet and see no funds, there are several possible explanations:
- The wallet is using a different derivation path than the one originally used.
- The funds are in a script type that the current wallet does not display, such as legacy, compatibility SegWit, or native SegWit.
- The original wallet used non-standard account behavior.
- A BIP39 passphrase was used when creating the seed, but you did not enter it during restoration.
- Older wallets may have stacked multiple address types under one visible account number.
A zero balance does not automatically mean loss. It often means the wallet is only looking at part of the tree created from your mnemonic.

Security warning before importing a seed
Before we get into the demo, I want to be clear about security.
Importing your recovery seed into Electrum makes that seed hot. That means it is present in software and can potentially be exposed if the environment is compromised. Because of this, you should not casually import a valuable seed into an ordinary desktop wallet just to test things out.
For this kind of search, I prefer using one of these approaches:
- Run Electrum inside Tails Linux, which provides a disposable, privacy-focused environment.
- Use Electrum on Android if you can verify the APK and are comfortable with that setup.
If the seed is already being used with a hardware wallet, my strong advice is still to reset that hardware device, generate a fresh new seed, and move recovered funds from the old wallet to the new offline wallet once you have found them. This reduces the risk of continuing to use an older seed that has now been exposed in software.
Running Electrum in Tails
For this demo, I boot into Tails Linux. The default settings are fine for a basic setup: start Tails and connect to Tor automatically.
Tails can be useful here because it is designed to run from removable media and does not leave persistent traces on the machine by default. That makes it better than using your normal desktop environment when you need to import a seed into software just to search for accounts.

There are two main ways to use Electrum in Tails:
- Use the version of Electrum bundled with Tails.
- Download and verify an Electrum image, then run it inside Tails if you want extra thoroughness.
For simplicity, I used the bundled Electrum in the video. If you are handling high-value funds or doing serious recovery work, verifying software is always a good habit.

Restoring a BIP39 mnemonic in Electrum
Once Tails is running and connected through Tor, open Electrum from the applications menu. You will get a warning that persistence is disabled for Electrum. That is expected in this setup.

To restore a BIP39 seed:
- Open the Electrum install wizard.
- Leave the wallet name as
default_walletor choose another name. - Click Next.
- Choose Standard wallet.
- Select the option saying you already have a seed.
- Enter your BIP39 recovery words.
- Open Options and select that this is a BIP39 seed.
- Confirm the checksum is okay, then continue.
Do not enter any real seed into an untrusted or ordinary environment just for testing. Use Tails, a verified Android setup, or another isolated method you trust.

Using Detect Existing Accounts to find hidden accounts
This is the part of Electrum I want more people to know about.
When restoring a seed, you can manually choose the script type and derivation path. But Electrum also has a Detect Existing Accounts button. This feature scans common standard and non-standard derivation paths and script types to look for accounts that already have history associated with your mnemonic.
This is especially useful when:
- You restored a seed but see zero balance.
- A wallet shows only part of the expected funds.
- The original wallet was an older mobile or desktop app.
- You are not sure whether legacy, compatibility SegWit, or native SegWit accounts were used.
- Someone may have accidentally created non-standard account paths.
In the demo, Electrum detected multiple accounts from the same seed:
- A BIP44 legacy account.
- Compatibility SegWit accounts.
- A second compatibility SegWit account.
- A native SegWit account.
- A non-standard legacy account.

This kind of configuration is common if the original wallet was something like Mycelium or Coinomi. Older wallets sometimes presented legacy, compatibility SegWit, and native SegWit accounts in a way that looked like one account to the user. Modern wallets often separate those into distinct accounts because each script type has its own address format and derivation behavior.
That means funds that once appeared “under Account 0” in an older wallet may now need multiple Electrum wallets or accounts to display fully.
Restoring all associated accounts
Once Electrum detects the possible accounts, you can restore them one by one.
In the demo, I restored each detected account so I could see where the funds were actually sitting. The important point is that one mnemonic can be associated with multiple accounts across different script types and derivation paths. A wallet that only shows one of those accounts will not show the full picture.
After restoring the relevant accounts, you may end up with several Electrum wallets open at once. Each one represents a different account derived from the same seed. That is normal when you are trying to locate all funds associated with a mnemonic.

In the video, one of those accounts matched what had been visible in the original wallet. The others contained funds that were not being shown there at all.

This is why I recommend Electrum for this kind of troubleshooting: it does a good job detecting non-standard setups, including cases where people may have used unusual combinations of script type and derivation path.
What wallet fingerprints tell you
Another useful part of this process is checking the BIP32 root fingerprint.
In Electrum, open Wallet Information for each restored account. Even though the accounts may have different script types and different derivation paths, they should share the same BIP32 root fingerprint if they were created from the same seed or seed plus passphrase.

When I compared all the Electrum wallets side by side, each had a different account configuration, but they all showed the same root fingerprint.

This is also useful when comparing wallets across software. In Sparrow, the equivalent value is called the master fingerprint. If the Electrum BIP32 root fingerprint matches the Sparrow master fingerprint, that gives you confidence that both wallets are using the same underlying seed material.

This does not prove where your funds are located, but it helps narrow down the problem. If the fingerprint matches what you expect, you can stop worrying about whether you typed in the wrong seed and instead focus on checking derivation paths, account numbers, script types, and passphrases.
Practical checklist for missing balances
If you have restored a BIP39 seed and the balance looks wrong, work through this list:
- Confirm the recovery words are entered correctly.
- Check whether the wallet asks for a BIP39 passphrase.
- Do not assume the funds are in Account 0 only.
- Use Electrum’s Detect Existing Accounts feature in a secure environment such as Tails.
- Restore each detected account and check its history.
- Compare script types: legacy, compatibility SegWit, and native SegWit.
- Check the BIP32 root fingerprint across wallets to confirm seed consistency.
- If the seed was exposed in software, consider moving funds to a fresh hardware wallet with a new offline seed once recovered.
When to get help
Everyone makes mistakes, especially when storing Bitcoin for long periods. The best protection is still good record keeping: clear notes about your wallet type, derivation paths, script types, passphrases, and fingerprints where appropriate.
If you are stuck, I do my best to reply to comments on the video. If you need one-on-one support with a recovery or lost funds situation, you can also request help through my recovery services and consultations page.
My hope is that you never need these tools. But if you do, knowing how to search for hidden accounts—and how to verify the seed with wallet fingerprints—can make a big difference.
Full video transcript
Auto-generated from the video and lightly corrected; timestamps open that moment on YouTube.
Introduction 0:00
So maybe you've got a situation where you've restored your recovery seed into your wallet but you're seeing a balance of zero. What are you going to do? I see situations like this all the time in these sort of recoveries and consultations that I do with people and while sometimes it's to do with things like using a BIP39 passphrase, other times it's to do maybe with compatibility issues between the wallet they originally used when they set things up versus the one they're trying to use now or maybe they've actually done something non-standard somewhere along the way by accident. So in this video, I'm just going to run through some powerful functionality in Electrum that is useful in this exact situation. It's actually been part of Electrum for a couple of years now, but it does seem to me that it's not nearly as widely known about, appreciated, or understood as it should be. And once I've run through that, I'll also just talk a little bit about wallet fingerprints and how they are a really powerful way to be able to make sure that you don't get your backups mixed up and you know that you are at least looking at the right wallet. So let's get into it. And if you haven't already done so, hit subscribe. That way you can stay in the loop for content i make to help you find your way in the crazy and often hostile environment that is cryptocurrency so just to start with let's say we had this seed here that we had had for a few years
Demo Wallet with Missing Funds 0:58
and we're going to restore it onto an Ellipal but when we paired this with our app had a look at balance we could see that there was only basically 68 cents there and hardly any transactions and this is pretty much the point where people start to panic now in this specific situation this is due to Elipal not following standards very well. If you were to store this seed on something like a Jade, Ledger, or Trezor, it would show up just fine. But anyway, let's just run through how you would use Electrum on Tails to find some of the other Bitcoin accounts that we can't seem to see with the Elipal. This will involve importing your recovery seed into Electrum, which will make your
Security Warning 1:34
recovery seed hot. So this is not a process you just want to do on your standard desktop environment. This is actually something you want to do in something like Tails Linux, which does come bundled with Electrum or if you're someone who has an Android smartphone you could use Electrum for Android on your phone as that will generally be a more secure environment than your standard desktop and you can also verify the APK for Electrum on your phone using the process that I cover in this video here and just like I often say in my other recovery videos with BTCRecover and stuff if this is a seed that you're using with a hardware wallet my strong advice is that even if you're using these precautions and running Electrum in Tails you should still you know reset that hardware device generate a new seed and then send the funds from this old wallet you've recovered onto a fresh new seed on your hardware wallet that will stay offline so you have been warned so basically I booted up into Tails and I'll just say start Tails because the defaults are all fine
Running Electrum in Tails 2:29
and we'll just go with the defaults and just use Tor automatically now there are two ways that you can use Electrum with Tails you can just use the Electrum that comes bundled with Tails which is probably fine or if you really want to be thorough you can actually follow the process to verify the GPG signature of an Electrum app image and then run that in Tails Linux using the process that I cover in this video here. For the sake of simplicity in this video I'll just be using Electrum bundled with Tails. So basically we'll just click on applications go into internet and choose Electrum Bitcoin wallet. It will warn us to say persistence is disabled for Electrum that's fine okay so basically on the electrum screen we'll just leave it as default wallet that's fine
Restoring our BIP39 Mnemonic in Electrum 3:13
we'll say next we'll say we have a standard wallet and we'll say that i already have a seed and we'll say next now this is where we enter in the seed phrase that i had before and given that this is electrum we also need to click on options and say that we have a bip 39 type of seed and say okay and then we can see it says the checksum is okay and we click next
Seaching for Existing Accounts 3:36
now this is what i actually want to show you so while we can manually choose the script type and derivation path in Electrum. There's also this feature here which says detect existing accounts and if I click on that basically what it will do is it will scan common paths and this includes both standard and non-standard derivation paths and script types we might have used. So it's not only found both a legacy and compatibility SegWit account for account zero but it's also found a second account you know account one for compatibility SegWit. It's found a native SegWit account as well as a non-standard legacy account and this kind of account configuration is actually very common if you were using something like mycelium or coinomi because how a lot of these older wallets used to work is they would give you a legacy segwit and native segwit account and sort of stack those three accounts on top of each other and the challenge with these kinds of wallets is that most modern wallet software will only use a single script type for each account and won't represent any funds that might have been spread across the different script types in the way that you would expect meaning you'll actually have to create multiple accounts to be able to access all of the funds that were previously sort of rolled into a single account. So in this instance this
Restoring All Accounts associated with the Mnemonic 4:44
standard BIP49 compatibility Segwit account is the one that I was showing on the Elipal and I just say okay it'll automatically populate this for me and if I say next I won't worry about a password and while we're waiting for that to sync I'll actually just add all the other accounts that had these funds in them. So there we go I've run through that process and found five different accounts all associated with that seed that all had funds and this first one here is actually the only one that Ellipal was showing me it wasn't giving me any visibility of the others at all and while it's important to say blue wallet does do something very similar to this when you import a seed into it i still found that electrum does a much better job particularly of detecting seeds that people have set up and accounts people set up in non-standard ways doing something like using say a native SegWit script type on a legacy derivation path or something like that. This is
Demonstrating Wallet Fingerprints 5:38
also a really good spot just to show you something helpful about wallet fingerprints and if I just go into wallet information for all of these accounts and if I just arrange these wallet information windows you'll see that despite the fact that each of these different wallets has a different derivation path and a different script type they all have exactly the same BIP32 root fingerprint And if we go over here and put that seed into Sparrow, we can see that what is called the BIP32 root fingerprint over here in Electrum is the master fingerprint here in Sparrow. So in terms of both record keeping and troubleshooting, if you keep track of your wallet fingerprint, you can be sure that you are looking at the correct account in terms of where you think your funds should be. And if you're doing something like troubleshooting, say a hardware wallet, offline signer, or something like that, if you know that the wallet fingerprint matches what you expect, you can at least panic a bit less because you can be sure that you have the right seed that you should expect, or the seed plus passphrase if you're using a passphrase, and you can know to focus instead on things like checking different derivation paths, checking different account types, and focusing here rather than wondering whether you actually have the right seed in the first place.
Conclusion 6:48
While you can manually go through checking all the different script types, account numbers, and derivation paths using a hardware wallet, and while some things like Ledger and Trezor do this very well, I still think it is very helpful to at least know about the tools that exist out there, particularly this functionality in Electrum. You know, my hope is that you actually never need to use it and that you keep good track of your notes, recovery seeds, and things like that. But the simple reality is everyone does make mistakes, particularly if you are storing funds for the long term. If you've had any experience with this kind of issue or are familiar with other tools that might be helpful, definitely leave a reply in the comments. likewise if you are actually having this problem yourself you know definitely just leave a reply in the comments I do my best to try and reply to all of them but if you're totally totally stuck and want one-on-one support you can also request that through my website here other than that stay safe thanks for watching I hope that was helpful hit like if you think that other people would find this video useful and hit subscribe if you'd like to be kept in the loop about future content I make that helps people stay safe in the crypto space and to recover if they get into trouble if you have any questions about this video or a topic that you'd like me to cover just leave a reply
Related guides
Stuck with a wallet recovery?
I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.
Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.
Found this useful?
These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.


