Exodus charges $0 to send — a stuck transaction can cost more

Why Is Your Exodus Transaction Stuck?

You hit send, the balance drops, and the confirmation never arrives. The uncomfortable part is that neither you nor Exodus can undo it — but you usually have more control than the "Pending" label suggests.

An Exodus transaction stalls because Exodus is a self-custody wallet: it signs and broadcasts your transaction to the blockchain, after which the network — not the company — decides when it confirms. Exodus cannot reverse, cancel, or force a broadcast transaction, since keys are generated and held on your device . Most transactions confirm within 5–60 minutes .

Delays trace back to one of four causes, and identifying yours determines the fix:

• Fee set too low for current mempool demand — the most common and the most fixable.
• Network congestion and mempool backlog, where even reasonable fees wait in line.
• Slow native block times on the chain itself, which no fee bump changes.
• Cosmetic sync lag — a block explorer shows "confirmed" while Exodus still displays "Pending." Refreshing the wallet resolves it; nothing is actually stuck.

One correction worth internalizing before you touch anything: cost and confirmation speed depend on transaction size in bytes and the fee rate you paid — not the dollar value being sent . A $50 Bitcoin send and a $50,000 one queue on identical terms.

Does Exodus Actually Charge a Fee to Send Crypto?

Exodus charges nothing to send, receive, or store crypto — 100% of what you pay goes to the blockchain itself, either to Bitcoin miners or to proof-of-stake validators, according to Exodus support documentation . That is a real distinction from custodial exchanges, which layer a withdrawal fee on top of the network cost. But a $0 wallet fee does not mean a cheap transaction. The network fee is the entire bill, and Exodus's default fee tier and per-platform controls decide how large that bill gets.

Bitcoin carries two hard amount rules inside the wallet. The minimum BTC send is 0.00000546 BTC, and any remaining balance below 0.00001501 BTC is added to the transaction fee as dust rather than left sitting in the wallet . Sweeping a wallet down to a near-zero balance therefore quietly donates the remainder to miners. Token sends add a second requirement: an ERC-20 transfer needs ETH in the same wallet to pay gas, so a wallet holding only USDT cannot move it .

Network cost varies by roughly four orders of magnitude across chains. The figures below come from live network fee-tracking data, not official Exodus pricing, and shift with congestion . Stablecoins follow the same pattern: moving USDT as an ERC-20 token typically costs far more than moving the same USDT on Solana .

Two Exodus-specific behaviours explain the "free wallet, expensive transaction" complaint. First, independent reviews report that during a mempool spike the app can default to a high fee to ensure speed, rather than the cheapest one that would still confirm . Second, the mobile app has been observed to over-simplify network fees, giving fewer sat/vByte controls than desktop . Custom fees are available on Mobile, Desktop, and the Web3 Wallet for both Bitcoin (in sat/byte) and Ethereum/ERC-20, where the figure you enter is the maximum you might pay, not a fixed charge .

One boundary matters for anyone planning around fees: custom fees are not supported inside Exodus Swap. For swaps, the wallet sets fees automatically from live network conditions, and you cannot dial them down . Sends give you the fee lever; swaps do not.

How to Confirm a Transaction Is Really Stuck

Before treating a transaction as stuck, verify it on the blockchain itself. Every Exodus send produces a unique transaction ID (TXID) that functions as a public blockchain receipt, and an explorer lookup will tell you within seconds whether the transaction is genuinely unconfirmed, already confirmed, or never broadcast at all . Exodus documents that most transactions confirm within 5–60 minutes, so anything meaningfully past that window is worth checking rather than waiting on .

Finding the ID takes a different path on each platform, and both are documented by Exodus support:

• Desktop: open the asset wallet, click the arrow next to the transaction, then copy the ID or click it to open the transaction directly in a block explorer.
• Mobile: tap the asset, scroll to the activity list, tap the transaction, then tap the ID to open it in an explorer or long-press to copy it.

The explorer page is the authoritative record. It typically shows the confirmation count, the sending and receiving addresses, the amount, the fee paid, and both created and confirmed timestamps . Cross-check that detail before concluding the wallet is wrong. There is a fourth, purely cosmetic failure case that this check resolves immediately: if the explorer shows the transaction confirmed while Exodus still displays "Pending," the problem is wallet sync, not the network, and refreshing the wallet clears it .

Token senders should check one more thing before assuming congestion. An ERC-20 transfer is settled by the Ethereum network, so it requires ETH held in the same wallet to pay gas . A token balance alone is not enough. If the wallet holds USDC or LINK but no ETH, the send cannot be funded, and what looks like a stalled transfer is a gas shortfall rather than a mempool backlog. The same principle applies on every chain: the native asset pays the fee, regardless of which token is moving.

If you are the receiver rather than the sender, this verification step is the entirety of your available action. You hold no lever over someone else's unconfirmed transaction — only the sender can accelerate it from their own wallet . Ask the sender for the TXID, look it up, and read the confirmation count. If the explorer shows the transaction confirmed on-chain but the funds have not been credited to your account on a centralized exchange or payment platform, the issue sits with that platform's internal crediting process, and their support team is the correct contact — not Exodus, which cannot see or influence another service's ledger .

Bitcoin Stuck? Decide Between RBF and CPFP

Exodus offers exactly two acceleration mechanisms for a stuck Bitcoin transaction, and which one is available to you was decided the moment you hit send. Replace-by-Fee (RBF) rebroadcasts a replacement transaction carrying a higher fee, but it only works if RBF was enabled on the original send and enough spare BTC sits at the sending address . Child-Pays-For-Parent (CPFP) is the fallback when RBF was never switched on: you spend the pending transaction's change output in a new, high-fee transaction, giving miners an economic reason to confirm both together. CPFP is Bitcoin-only and requires that a change output exists .

The RBF flag is the pivot, and most users set it without realizing. Choosing a custom Bitcoin fee in sat/byte automatically enables RBF on that send; taking the recommended fee leaves RBF off by default unless you enable it manually in a supported flow . Since Exodus can default to a faster, costlier fee tier during congestion, the users most likely to get stuck are precisely those who overrode the default downward — who, conveniently, also enabled RBF in the process .

Both routes are available from Exodus Mobile and Desktop, and both share the same hard prerequisite: spare BTC in the wallet to pay for the bump . If you swept the address to zero, neither mechanism can be funded, and the decision is made for you. Exodus is also direct about the price of impatience.

"Accelerating a transaction can cost more than a regular transaction fee." — Exodus support documentation on accelerating a stuck Bitcoin, Ethereum, or ERC-20 transaction (source: Exodus Support)

Run the cost arithmetic before you commit. Live fee-tracking data puts a typical Bitcoin network fee at roughly $1 to $5, rising well beyond that during mempool congestion . A bump that has to outbid current demand can land meaningfully above that, and with CPFP you are paying for two transactions' worth of block space rather than one. For a small transfer, the acceleration fee can exceed a double-digit percentage of the amount in flight — at which point waiting is the rational choice, not the passive one. Also note that the minimum BTC send is 0.00000546 BTC, and any residual balance below 0.00001501 BTC is swept into the fee as dust rather than left at the address — which is why a "spare BTC" balance can turn out to be unusable in practice.

If RBF was off and no change output exists, or if the sending address holds nothing spare, stop looking for a lever. There is none, and no support ticket will create one — the transaction sits in the mempool until it confirms or is dropped, and that outcome is covered further down.

Ethereum and ERC-20: A Narrower Fix

Ethereum and ERC-20 acceleration in Exodus works only when the original send used a custom fee, and only when the wallet still holds enough ETH to fund the higher bid . There is no Ethereum equivalent of Child-Pays-For-Parent to fall back on, so a stuck send that went out at the recommended fee has no manual lever at all — the two Bitcoin escape routes collapse into one narrow path on Ethereum . That single condition, set at the moment of sending, decides everything that follows.

The gas requirement is the second trap, and it catches token senders more often than ETH senders. Gas on Ethereum is paid in ETH regardless of what is being moved, so an ERC-20 transfer of USDT, USDC, or any other token needs a separate ETH balance in the same wallet . A wallet that was funded with just enough ETH to cover the original fee has nothing left to bid with, and the acceleration option is unavailable in practice even when it is technically eligible. The bump costs more than the original fee by definition — that is the entire mechanism — so the buffer needs to be meaningful, not symbolic.

Custom ETH and ERC-20 fees are available on Mobile, Desktop, and the Web3 Wallet, and the figure entered is a maximum the transaction might pay, not a fixed charge . That distinction is worth internalizing before the next send: setting a generous ceiling does not mean paying it, because the network charges what current conditions require up to that limit. Live fee-tracking data puts typical Ethereum network costs at roughly $1–$20 per transaction , with a USDT transfer running about $2–$10 as an ERC-20 against under $0.001 on Solana . A higher ceiling is cheap insurance relative to the cost of a send that sits unconfirmed with no way to raise it.

Exodus Swap is the exception that removes the choice entirely. Custom fees are not supported inside the swap flow — Exodus sets swap fees automatically from live network conditions . Because acceleration requires an original custom fee, a swap leg that stalls cannot be manually bumped, and no configuration change made afterward alters that. Practical takeaways for anyone moving ETH or tokens:

• Use a custom fee on any send you might need to accelerate — it is the only thing that preserves the option.
• Keep an ETH reserve beyond the estimated fee, separate from the token amount, or acceleration is unavailable regardless of eligibility.
• Treat swaps as unaccelerable and time them against calmer network conditions rather than planning to fix them mid-flight.
• Consider the network itself a fee decision — the same stablecoin costs orders of magnitude less outside Ethereum mainnet .

No Acceleration Option? What Actually Happens Next

When neither Replace-by-Fee, Child-Pays-For-Parent, nor a custom-fee bump is available, the only remaining remedy is to wait for the network mempool to drop the transaction, and Exodus states plainly that there is no fixed timeframe for that to happen . This is the outcome for a recommended-fee Bitcoin send with RBF disabled and no change output to spend, for an Ethereum or ERC-20 send that used the default fee tier rather than a custom one, and for anything routed through Exodus Swap, where fees are set automatically and custom values are not supported . Waiting is not passivity here — it is the documented process.

The critical point during that window: a dropped mempool transaction returns your balance, it does not destroy it. Because Exodus is non-custodial and the keys never leave your device, an unconfirmed transaction has moved no coins — it has only been broadcast as a request that miners or validators declined to include . Once nodes evict it from their mempools, the funds reappear in the wallet balance and can be resent at a higher fee rate . The practical mistake in this window is panic: sending a second payment from another wallet to "fix" a delivery that has not failed, only to have the original confirm hours later and double the payment.

What to do while waiting, in order:

• Recheck the transaction ID on a block explorer, not just the app — a confirmed on-chain transaction still showing "Pending" in Exodus is a wallet sync issue that a refresh clears .
• Do not delete or reinstall the wallet to force a resend. On light-support networks, history is stored locally rather than synced, and deleting or restoring erases it .
• Plan the replacement fee before the drop, so the resend goes out at a rate matched to current demand rather than repeating the original mistake.

Inbound stuck payments follow a different rule entirely: the receiver has no lever. Acceleration can only be performed from the wallet that signed and broadcast the transaction, so the sender must act — the receiver's only actions are checking the transaction ID on an explorer and, where the transaction is confirmed on-chain but not credited, contacting the sending centralized platform directly . Chasing a delayed incoming payment through anything other than the sender or that platform wastes time you could spend confirming the transaction actually exists.

Exporting Transaction History for Taxes or a Dispute

Exporting your Exodus history produces a CSV file on your own device, not a statement from a company that holds your records. On Desktop, open the History icon, select the three-dot menu, and choose Export All Transactions; the file writes to a local folder named exodus-exports, and every timestamp inside it is recorded in UTC rather than your local time zone . You can export everything or filter to sent, received, or swapped transactions, and the Web3 Wallet extends the categories to include swap, NFT, and other activity . Because the export is self-custody data, treat it as a working record you are responsible for preserving — nobody else keeps a copy.

That responsibility becomes concrete on networks Exodus classifies as having "light support." On those chains only send transactions appear in the app and in the export, balances remain accurate, and the history itself is stored locally rather than synced from a server. Deleting the wallet or restoring it from your 12-word recovery phrase erases that local record permanently, even though the underlying on-chain activity is untouched . If you are about to reinstall, migrate devices, or restore after a suspected compromise, export first.

History depth also caps by chain. Exodus states that Base displays approximately 1.5 years of activity and BNB Smart Chain approximately 2 years, with anything older retrievable only from a block explorer . For a 2023 Base position or an early BNB Smart Chain trade, the CSV will simply not contain the row — and a tax preparer reading only that file will conclude the transaction never happened. The fix is the same tool used to verify a stuck send: pull the transaction ID and reconstruct the entry from explorer data, which shows confirmations, sending and receiving addresses, amount, fee, and created and confirmed timestamps .

Three practical steps close the gap between what the export gives you and what a filing or a dispute requires:

• Export on a schedule, not at the deadline. Quarterly exports protect against light-support history loss and against chain depth caps quietly rolling older rows out of view.
• Run the CSV through a tax tool. CoinLedger, CoinTracking, and Waltio all ingest the Exodus CSV directly, which removes manual re-entry and its transcription errors .
• Reconcile UTC against your jurisdiction. A late-evening send in the Americas can land on the following calendar day in UTC — enough to shift a transaction across a tax year boundary or misalign a dispute timeline.

For a dispute with a counterparty or an exchange, the transaction ID carries more weight than the CSV: it is the blockchain receipt anyone can independently verify, while your export is a local file only you produced. Send both — the ID as the evidence, the CSV as the context.

Compromised Wallet or Fake Support Scam? Know the Difference

A compromised Exodus wallet and a scam support page are two different threats, and confusing them costs money in opposite directions. Compromise means someone else holds your keys: anyone with the 12-word recovery phrase, private keys, wallet password, or passkey backup — or physical or remote access to your device — can sign and broadcast transactions you never approved . A fake support channel is the entry point that hands those keys over. Both hinge on the same fact: in self-custody, a signature is final and no company can reverse it.

Read the ledger before you panic. Small, unfamiliar ETH-denominated entries are usually ordinary side effects of ERC-20 activity — a token transfer burns ETH gas from the same wallet, and that gas line looks like an unexplained outflow to anyone reading only the fiat column . The real compromise signal is different in kind, not degree: a large transfer of principal to a destination address you do not recognize . Open the transaction ID in a block explorer and check the receiving address against your own records before drawing a conclusion.

If the signal is real, Exodus's guidance is blunt and time-sensitive: move remaining assets to a newly generated wallet immediately, and stop sending anything further to the compromised one . Restoring the same 12-word phrase into a fresh install does nothing — the phrase is what leaked, so the new wallet inherits the same exposure. Generate a new recovery phrase on a device you trust.

"Exodus will never ask for your password, 12-word recovery phrase, private keys, or a sync QR code," states the company's official support documentation, which lists email and in-app or website chat as the only legitimate contact routes (source: Exodus Support).

That last point deserves emphasis because search results for stuck-transaction queries are heavily polluted with counterfeit help pages advertising phone numbers. Exodus operates no phone line and no Telegram support — the official channels are email at support@exodus.com and chat inside the app or on the website . Any "agent" who calls, asks you to scan a sync QR code, or requests your recovery phrase is running a theft, not a support ticket. A May 2025 breach exposed roughly 101,597 user email addresses with no key compromise , which means phishing mail addressed to you by name is plausible and does not prove the sender is legitimate.

The concrete takeaway across this whole guide: a stuck transaction is a fee problem with mechanical fixes — RBF, CPFP, or patience while the mempool clears — while an unauthorized transaction is a key problem with exactly one fix, executed fast. Diagnose which one you have by checking the destination address on a block explorer first. If it is yours, wait. If it is not, move funds now and contact Exodus only through its documented channels — never a phone number you found in a search result.

Last updated: 2026-09-07. Reviewed against Exodus official support documentation and the company's Q2 2026 financial disclosures.

Frequently asked questions

Does Exodus charge a fee for a stuck or accelerated transaction?

No. Exodus charges no fee to send, receive, or store crypto, and 100% of the network fee goes to Bitcoin miners or proof-of-stake validators . Accelerating a stuck transaction is different from cancelling it: Replace-by-Fee rebroadcasts a replacement at a higher fee, and Child-Pays-For-Parent spends the change output with a fee large enough to pull the parent along. Both pay an additional network fee on top of what you already committed, and Exodus explicitly warns that acceleration can cost more than an ordinary transaction fee . Budget for that before bumping a low-value send — live fee-tracking data puts typical Bitcoin network costs at roughly $1–$5, rising well beyond that during congestion, so a bump on a $30 transfer can still consume a meaningful share of the amount . Note also that swaps are priced differently: the Exchange Aggregator has no labeled trading fee, only an embedded spread starting around 0.5% and often running higher .

How long can an Exodus transaction stay pending?

Most confirm within 5 to 60 minutes, according to Exodus support documentation . Beyond that window, the usual causes are a fee set too low for current demand, mempool backlog during congestion, or a chain with inherently slow block times. A transaction priced below what miners are currently accepting can sit for hours or days. Exodus states there is no fixed timeframe for when a node will drop an unconfirmed transaction from its mempool . When the drop does occur, the funds reappear in your wallet and you can resend at a competitive fee rate. Until then the coins are neither spent nor spendable, which is the practical cost of underpricing a send. If waiting is not acceptable and you are on Bitcoin, acceleration is the only lever — and it is only available if the original send left you a usable path.

Can Exodus cancel a stuck transaction for me?

No. Exodus is a self-custody wallet: keys are generated and held on your device, signing happens locally, and the company cannot move funds, reverse a broadcast, or force a confirmation . Once a transaction is broadcast it belongs to the network, not to any company. That leaves exactly three outcomes: it confirms on its own, you replace or accelerate it via RBF or CPFP, or the mempool eventually drops it and the funds return to your wallet. Support staff can explain those mechanics but cannot execute them for you. This is also a useful scam filter — anyone claiming they can "reverse" or "unlock" your transaction is not Exodus. Official contact is limited to email at support@exodus.com and in-app or website chat; Exodus provides no phone or Telegram support, and staff will never request a password, 12-word phrase, private key, or sync QR code .

Why is my Bitcoin transaction stuck with no way to accelerate it?

Both Bitcoin acceleration routes have preconditions, and a normal send can fail all of them. RBF requires that Replace-by-Fee was enabled on the original transaction; setting a custom BTC fee in sat/byte enables RBF automatically, while recommended-fee sends have it off by default unless you turned it on in a supported flow . CPFP is the fallback, but it is Bitcoin-only and requires a change output from the pending transaction — send your entire balance and there is no change to spend . Either route also needs spare BTC at the sending address to fund the higher fee. If RBF was off, there is no change output, and no spare balance, there is no lever: wait for mempool expiry, then resend with a custom fee so RBF is enabled next time. Also keep the amount rules in mind — the minimum BTC send is 0.00000546 BTC, and any remainder below 0.00001501 BTC is added to the fee as dust rather than left in the wallet .

My transaction shows confirmed on a block explorer but pending in Exodus — what's wrong?

Nothing is wrong with the transaction. When an explorer shows confirmations but the app still displays "Pending," that is a wallet sync display issue, and refreshing the wallet resolves it . The blockchain is the authoritative record; the wallet interface is a view of it. Verify by locating the transaction ID — on Desktop, open the asset wallet, click the arrow next to the transaction, then copy or click the ID to open it in an explorer; on Mobile, tap the asset, scroll to activity, tap the transaction, then tap to open or long-press to copy . If the explorer shows confirmations, sending and receiving addresses, amount, fee, and a confirmed timestamp, the send is complete. Do not accelerate a transaction that has already confirmed — you would only be paying a second network fee for nothing.

The transaction confirmed on-chain but the recipient says it never arrived. What now?

Split the question by destination. If the receiving address belongs to another self-custody wallet, an on-chain confirmation means the funds are at that address, and the recipient needs to check the correct asset and network in their own wallet — a token sent on the wrong network will not show under the expected asset. If the destination is a centralized exchange or payment platform, the credit is that platform's responsibility once the transaction is confirmed, and the recipient should contact its support with the transaction ID . For an inbound transaction that is still unconfirmed, the receiver has no lever at all: only the sender can accelerate from their own wallet, because only the sender holds the keys to the inputs . In every case the transaction ID is the receipt that settles the dispute.

Will my Exodus CSV export capture every transaction for tax filing?

Not always, and the gaps are documented. Desktop exports all assets or filtered sent, received, and swapped transactions via the History icon, the three-dot menu, then Export All Transactions, writing to an exodus-exports folder, with timestamps in UTC . Three limitations matter. Some networks have "light support," where only send transactions appear in-app and in exports, and history is stored locally rather than synced — deleting or restoring the wallet erases it. Others retain only recent history: Exodus states Base covers approximately 1.5 years and BNB Smart Chain approximately 2 years, with older activity available only on block explorers . Third-party tools including CoinLedger, CoinTracking, and Waltio ingest the CSV directly, but they can only import what the file contains. Reconcile the export against block explorer data for any chain you used heavily before treating it as a complete record.

Enjoyed this article? Subscribe to get new stories by email whenever they're published.

Subscribe