How to see all wallet addresses in Exodus? (UTXO Management)

Accessing Wallet Addresses in Exodus Desktop

1. Launch the Exodus desktop application on your Windows, macOS, or Linux system.

2. Navigate to the asset tile of the cryptocurrency you wish to inspect—such as Bitcoin or Litecoin—by clicking directly on its icon in the main wallet view.

3. Click the Receive button located beneath the asset balance. A modal window will appear displaying the current deposit address.

4. Scroll down inside that modal to locate the “View all addresses” link. Clicking it reveals a list of previously generated receiving addresses tied to that specific asset.

5. Each displayed address is labeled with its creation timestamp and usage status—whether used or unused—providing immediate visibility into UTXO distribution across addresses.

Understanding Address Generation Logic

1. Exodus employs hierarchical deterministic (HD) wallet architecture compliant with BIP-44 standards for Bitcoin and compatible chains.

2. New addresses are derived sequentially from the master seed but only revealed upon explicit user action—such as clicking “Receive” multiple times or accessing the full address list.

3. Unused addresses remain dormant until funds are sent to them; they do not auto-generate beyond a lookahead gap of 20 addresses by default.

4. Each address corresponds to a unique public key hash, and every incoming transaction creates one or more UTXOs associated exclusively with that address.

5. The wallet does not consolidate UTXOs automatically during normal operation—manual coin control is unavailable in Exodus’s UI, meaning transaction inputs are selected algorithmically by the client.

Mobile App Limitations on Address Visibility

1. The Exodus iOS and Android applications restrict access to historical receiving addresses for security and interface simplicity reasons.

2. Users can only view the most recently generated address per asset via the Receive screen.

3. There is no built-in option to scroll through prior addresses or export a full list of derived addresses from the mobile interface.

4. Attempting to generate new addresses repeatedly may result in gaps—some addresses might never appear unless explicitly triggered by a receive action followed by manual navigation.

5. This design decision prioritizes ease of use over granular UTXO-level transparency on smaller screens.

Recovery Phrase and Address Derivation Verification

1. All addresses visible in Exodus are deterministically derived from the original 12-word recovery phrase entered during wallet setup.

2. You can independently verify any address using open-source BIP-39/BIP-44 derivation tools—inputting the same mnemonic and path (e.g., m/44'/0'/0'/0/0) reproduces the first Bitcoin receive address.

3. Exodus uses hardened derivation paths, ensuring private keys cannot be compromised even if extended public keys are exposed.

4. No server-side storage of addresses or transaction history occurs—the entire derivation process runs locally within the app binary.

5. Exporting or backing up individual addresses is unsupported; the sole authoritative backup remains the 12-word phrase stored offline.

Frequently Asked Questions

Q: Can I manually choose which UTXOs to spend when sending Bitcoin from Exodus?A: No. Exodus does not expose coin control features. Input selection follows internal heuristics based on fee optimization and address reuse avoidance.

Q: Why do some addresses show “Unused” while others display “Used” even though I never sent funds to them?A: Exodus pre-generates addresses ahead of usage. An “Unused” label indicates the address has received zero confirmed transactions; “Used” means at least one inbound transaction exists, regardless of whether you initiated outgoing transfers from it.

Q: Does Exodus support Bech32 address format for Bitcoin?A: Yes. Exodus automatically generates native SegWit (bech32) addresses by default for Bitcoin, improving transaction efficiency and reducing fees.

Q: If I delete and reinstall Exodus, will my old addresses reappear?A: Yes—as long as you restore using the original 12-word recovery phrase, all previously derived addresses—including those marked “Unused”—will regenerate identically.