Why a Base swap can stay pending

A Base swap stays pending when its transaction has not yet been included in a Base block, or when the wallet has not updated its display. A swap is a transaction that asks a smart contract to exchange one token for another under stated conditions. Its status depends on what happened onchain, not just on the spinner in the app.

Some swaps also require a separate token approval transaction before the trade. Check the activity list for both entries: an approval can be complete while the swap itself is still pending. For a wider account of how a Base swap fits into an exchange trade, see the fuller explanation of what an exchange does and what a trade returns.

What does pending mean on Base?

Pending means the wallet has not shown the swap as complete; it does not, by itself, tell you whether the transaction reached the network. Once signed, the transaction is sent to Base’s sequencer, which orders transactions and produces Layer 2 blocks. The wallet can show pending while it waits for a transaction receipt, or while its connection to the network or activity view catches up.

Use the transaction hash to check the transaction on a Base block explorer. A visible transaction with a successful receipt was executed. A failed receipt means it was included but the swap call reverted; the trade did not complete, though the transaction may still have used gas. If the hash is not found, the explorer cannot confirm inclusion yet. Check that you are viewing the right network and account before drawing a conclusion.

Why can a swap get stuck?

A transaction may wait because its fee is too low for current conditions, because an earlier transaction from the same wallet is unresolved, or because the wallet has not refreshed its status. Ethereum-style accounts process transactions in nonce order: each nonce identifies a transaction’s position for that account. A later transaction can be held up behind an earlier one with a lower nonce.

The swap can also be included and fail during execution. The token price may have moved beyond the trade’s slippage limit, liquidity may not support the quoted amount, or a contract condition may have reverted. In that case, “pending” should eventually change to a failed status once the wallet reads the receipt. Repeating the swap with a higher slippage limit may allow a worse price, so review the quote and limits before signing again.

What should you check before retrying?

Start with the transaction hash, then check the wallet’s activity and the trade details. These checks distinguish a delayed display from a transaction that still needs attention:

• Confirm the transaction is on Base and belongs to the wallet address you used.
• Check whether the approval and swap are separate transactions, and whether either has a receipt.
• If an earlier transaction from the same address is pending, resolve that nonce first; use the wallet’s replacement option only if you understand its fee and replacement terms.
• If the swap failed, inspect the reason and review the token pair, amount, available balance for fees, and slippage setting before creating a new transaction.

Base distinguishes blocks that are sequenced but not yet derived from Layer 1 data from blocks that are safe or finalized. That distinction concerns the chain’s confirmation status; it is separate from whether a particular swap succeeded. For most users, the practical check is the transaction receipt: pending means wait or investigate, success means the contract call executed, and failure means the swap did not.