HD Wallet Derivation Path Builder
Build and decode BIP-32 derivation paths, see which address type each purpose produces, and understand why the same seed shows different balances in different wallets.
Last reviewed by the Radiatus Cloud team
Need this done properly for your business?
Radiatus delivers secure cloud, DevOps & compliance engineering.
One seed produces different addresses in different wallets
A recovery phrase does not determine an address. It determines a master key, and the derivation path decides which of the roughly four billion child keys per level you actually use. Two wallets given the same phrase and using different default paths will show different addresses and different balances, and both are correct. This is the single most common cause of "my funds are missing after restoring", and the funds are almost always at a path the restoring wallet did not look at.
The purpose field is what selects the address type
The second element of a path, called purpose, is hardened and conventionally states which standard applies: 44 for legacy addresses, 49 for wrapped SegWit, 84 for native SegWit, and 86 for Taproot. It is a convention rather than an enforcement, so a wallet can derive any key type from any path, and some do. The convention exists so that a scanning wallet knows where to look, and a wallet that ignores it will miss funds that are genuinely there.
Hardened derivation is what stops one leaked key exposing the rest
A hardened child key cannot be derived from the parent public key, only from the parent private key. That matters because with non-hardened derivation, someone holding the extended public key and any single child private key can compute the parent private key and therefore every sibling. The account level is hardened for exactly this reason, which is why an extended public key can be given to a watch-only wallet or an accountant without exposing the account itself.
Related tools
- Ethereum Unit Converter — Convert between Wei, Gwei, and Ether units.
- Gas Fee Calculator — Calculate transaction costs based on gas price and limit.
- IPFS CID Generator — Generate IPFS Content Identifiers (CID) from text or files.
- Wallet Address Validator — Validate Ethereum and Bitcoin wallet addresses.
Frequently Asked Questions
Why do two wallets show different addresses from one seed?
Because they use different default derivation paths. The seed determines a master key; the path selects which child key is used, and both wallets are correct about their own path.
What do 44, 49, 84 and 86 mean?
The purpose field, indicating legacy, wrapped SegWit, native SegWit and Taproot respectively. It is a convention that tells a scanning wallet where to look rather than something the protocol enforces.
What does the apostrophe mean?
Hardened derivation. A hardened child cannot be derived from the parent public key, which is what prevents one leaked child private key plus the extended public key from exposing every sibling.
Can I safely share an extended public key?
It lets someone see every address and every balance under it, which is why watch-only wallets work. Combined with any one non-hardened child private key it exposes the whole branch, so treat it as sensitive.
What is the change field for?
Zero for receiving addresses and one for change addresses. A wallet that only scans the receiving branch after a restore will miss change outputs, which is a common way a restored balance looks too small.
Privacy & Security
Everything runs in your browser; nothing is uploaded.
How to Use
Choose a purpose and coin to build the derivation path.
Disclaimer: This tool is provided "as is" without warranty of any kind. Results are for educational and utility purposes.