Cake Wallet transaction pending or stuck

Quick steps

1. Copy the transaction ID. Open the transaction in History and copy its transaction ID from the details screen.
2. Check a block explorer. Look up the ID on an explorer for that coin to see whether it is unconfirmed in the mempool or missing from the network.
3. Make sure the wallet is synced. Confirmations only update when the wallet is synced, so fix any sync problem or switch node first.
4. Bump the fee on Bitcoin. For an outgoing, unconfirmed Bitcoin transaction, tap Bump fee, choose a higher fee and send the replacement.
5. Wait on other coins. For Monero, Litecoin and EVM chains, wait for confirmation; Cake Wallet offers no bump option for them.
6. Ask support before resending. If no explorer finds the transaction after a long time, contact support before sending again so you do not pay twice.

A transaction is "pending" when it has been broadcast but not yet included in a block. New transactions appear in History straight away, and the details screen shows the number of confirmations, the fee, the transaction ID and a "View in Block Explorer" link (Cake Wallet docs, 2026). First find out whether the network has the transaction at all, then follow the section for your coin.

First: is the transaction on the network?

1. Open the transaction in History and copy the transaction ID.
2. Look it up on a block explorer for that coin. Type the explorer's address yourself rather than following links from strangers.
3. If the explorer shows it as unconfirmed, it is waiting in the mempool. If the explorer cannot find it, it probably never reached the network.

Cake Wallet's docs say pending transactions on chains other than Bitcoin usually confirm on their own and may just take longer when the network is busy (Cake Wallet docs, 2026). Low-fee transactions can take hours or even days.

Bitcoin: use Bump fee (RBF)

Cake Wallet supports Replace-by-Fee for Bitcoin. To speed up a stuck send, open the transaction in History, tap Bump fee, set a higher fee and tap Send. The app then broadcasts a replacement that pays more.

According to Cake Wallet's docs and code, the Bump fee option appears only when all of these are true (Cake Wallet docs, 2026):

• The wallet is a Bitcoin wallet. Bumping is not offered for Litecoin, Bitcoin Cash, Dogecoin, Decred, Monero, Zano, Zcash or EVM chains.
• The transaction is outgoing. You cannot bump a payment you received.
• It is still unconfirmed and replaceable. RBF is on for most transactions, but not for a transaction that spends unconfirmed inputs.
• The recipient was not a Silent Payments (sp1) address.

If the replacement fails, you may see Transaction has unconfirmed inputs and failed to replace by fee. In that case you cannot bump this transaction; wait for it, or for the transaction it depends on, to confirm. If a send is refused for a low fee, Cake Wallet's docs describe the error Error: Transaction submission failed and advise resending with a higher fee.

To avoid stuck sends, choose a higher priority before you send. Bitcoin priorities show an estimated time and a sat/vbyte rate, Medium is the default, and Custom lets you set the rate yourself. More in Cake Wallet for Bitcoin and fees.

Monero

Monero blocks come about every two minutes, so a send normally gets its first confirmation quickly. Common reasons it seems stuck:

• The wallet or node is behind. If the wallet is not synced, confirmations do not update. Let it sync, or change node.
• Locked change. Your Available Balance drops after a send because the change is locked for about 10 blocks. That is normal, not a stuck transaction.
• The node did not relay it. If no explorer finds the transaction after a long time, it may not have reached the network. Cake Wallet's documentation does not describe a rebroadcast button. Switch to a different node, let the wallet sync, and contact support before sending again so you do not pay twice.

For future sends, Monero priorities include Automatic (the default) and higher levels that pay more for faster confirmation. Large payments made from many small inputs can trigger This payment would be split into N transactions. Send smaller transaction to yourself first. Send a smaller amount to yourself to combine inputs, then retry.

Litecoin

Litecoin blocks come about every 2.5 minutes. There is no Bump fee in Cake Wallet for Litecoin, so check the transaction on an explorer and wait. Cake Wallet's docs say a Litecoin Commit error is fixed by force-closing the app, letting it sync fully and sending again. For MWEB, moving coins between the standard and private balance needs six confirmations, so a peg-in or peg-out will look pending for a while (Cake Wallet docs, 2026). See Litecoin MWEB.

Ethereum and other EVM chains

On Ethereum, Polygon, Base, BNB Smart Chain and similar networks, fees are gas paid in the chain's native coin. Sending USDT on Ethereum therefore needs some ETH in the same wallet. Cake Wallet's documentation does not describe a speed-up or cancel option for EVM transactions. If a send is pending, check it on the chain's explorer and wait; choosing Fast or Medium priority next time reduces the risk. If you see RPCError: got code -32000 with msg "execution reverted", Cake Wallet advises trying a different node, then force-closing and restarting the app.

Pending sends to an exchange or swap

Cake Wallet warns that slow, low-fee transactions can delay or cancel exchanges. If your deposit to a swap is still unconfirmed, the trade will wait. See exchange stuck.

Whatever the coin, nobody can "speed up" a transaction for you in exchange for your seed or a fee paid to a stranger. Cake Wallet never asks for your seed and never messages you first.

Frequently asked questions