Mnemonic to Address

What is Mnemonic to Address?

Mnemonic to Address is a secure client-side HD wallet tool that derives cryptocurrency addresses, public keys, private keys and account extended public keys (xpub/ypub/zpub) from BIP39 mnemonic seed phrases. It supports multiple blockchain networks including Bitcoin (with all address types: Legacy, Nested SegWit, Native SegWit and Taproot), Ethereum and EVM chains, Solana, XRP, TRON, Dogecoin, Cardano, and Bitcoin Cash.

It can also look up the on-chain balance of every derived address so you can quickly find the funded ones, and lets you reveal each private key in the correct import format (WIF for Bitcoin-family coins, 0x-hex for EVM/TRON, base58 secret key for Solana) for sweeping or migrating funds. Private keys are masked by default and only shown after an explicit confirmation.

All cryptographic operations and key handling run entirely in your browser - your mnemonic phrase and private keys are never transmitted to any server. Only public addresses are sent to balance APIs, ensuring maximum security and privacy.

Supported Blockchains

What is a BIP39 mnemonic phrase?

A BIP39 mnemonic phrase (also called seed phrase or recovery phrase) is a set of 12 or 24 words that serves as a human-readable backup of your cryptocurrency wallet. It can deterministically generate all your private keys and addresses across multiple blockchains.

Is it safe to enter my mnemonic here?

Yes. This tool runs 100% client-side in your browser. Your mnemonic phrase is never sent to any server. You can verify this by disconnecting from the internet after loading the page - the tool will continue to work. For maximum security, use this tool on an offline device.

What is the BIP39 passphrase?

The BIP39 passphrase (also called 25th word) is an optional extra layer of security. When used, it creates a completely different set of wallet addresses. If you set up your wallet with a passphrase, you must enter the same passphrase here to derive the correct addresses.

What are the different Bitcoin address types?

Bitcoin has 4 main address types: Legacy (1...) using P2PKH from BIP44, Nested SegWit (3...) using P2SH-P2WPKH from BIP49, Native SegWit (bc1q...) using P2WPKH from BIP84, and Taproot (bc1p...) using P2TR from BIP86. Native SegWit and Taproot offer lower transaction fees.

Why do Solana show two derivation paths?

Different Solana wallets use different derivation paths. Phantom and Solflare use m/44'/501'/x'/0' while Trust Wallet and Sollet use m/44'/501'/x'. This tool supports both to ensure compatibility with all major wallets.

What are the BIP44 variants for Bitcoin?

Some wallets incorrectly use the BIP44 path (m/44'/0'/0'/0/x) for all Bitcoin address types instead of the proper BIP49/84/86 paths. This tool provides these non-standard variants (marked with 'BIP44') for compatibility with such wallets.

Can I export the private key, and what format is it in?

Yes. Click the key icon on any address row to reveal its public key and private key. Private keys are masked until you confirm a warning. The format matches what wallets expect: Bitcoin, Bitcoin Cash and Dogecoin use compressed WIF (starting with K, L or similar; Dogecoin uses its own version byte); Ethereum, all EVM chains and TRON use a 0x-prefixed 32-byte hex key; Solana uses the 64-byte base58 secret key that Phantom accepts; Cardano shows the extended private key (kL||kR hex). You can also tick 'Include private keys in CSV' to export them in bulk. Everything stays in your browser - keys are never uploaded.

What is an xpub and how do I set up watch-only monitoring?

An extended public key (xpub) is derived at the account level (e.g. m/84'/0'/0') and can generate every receiving address for that account without exposing any private key. This tool shows the account xpub for each group, re-encoded to the correct SLIP-132 prefix: zpub for Native SegWit (BIP84), ypub for Nested SegWit (BIP49), and standard xpub for Legacy, Taproot and EVM. Import the xpub/ypub/zpub into a watch-only wallet (Electrum, Sparrow, BlueWallet, Trezor Suite) to track balances and receive funds while your seed and private keys stay offline.

How do I confirm these addresses match my Ledger, Trezor, MetaMask or Electrum wallet?

Use the same derivation path and standard your wallet uses. MetaMask and most EVM wallets use m/44'/60'/0'/0/x (the EVM group here, with EIP-55 mixed-case checksum). Electrum and Sparrow default to Native SegWit (BIP84, bc1q) - match the zpub or the index-0 address. Ledger and Trezor expose Legacy, Nested SegWit, Native SegWit and Taproot - pick the matching group. If the first address matches, the whole account matches because they share the same xpub. The mixed-case EIP-55 checksum is purely a typo guard; an address is valid regardless of casing, so compare case-insensitively if needed.