Four Checks for a Pending Swap During a Base Outage

During a Base outage, a pending swap may be waiting for the sequencer, missing from the status source you checked, or already included while your wallet still shows it as pending. The sequencer receives transactions and puts accepted ones into Base blocks; the swap contract only reads the pool’s reserves when that transaction executes. Check the network, transaction, account nonce and final swap result before trying again.

Is Base’s transaction service affected?

Start by checking whether the problem is specific to Base or to the wallet or app you used. Base’s status page reports components such as block production, the public RPC and the transaction pool. Those components do different jobs: an RPC endpoint lets your wallet submit transactions and read chain data, while the sequencer orders transactions into blocks. A problem in one can look like a general outage from inside an app.

Check the incident details and their timestamps, then note whether blocks are still advancing. A wallet can fail to refresh even while Base is producing blocks; conversely, an RPC may accept a request without the transaction being included. For a refresher on the contract and pool mechanics, see how a Base swap interacts with a liquidity pool. That distinction matters here: a transaction waiting to execute has not yet reserved the pool’s tokens.

What does the transaction hash show?

Open the transaction hash in a Base block explorer and check its network, sender, nonce, status and receipt. A hash identifies the signed transaction; a receipt appears only after the transaction is included in a block. If the explorer has no record, the wallet may have failed to submit it or the explorer may not have received the transaction yet. If it says pending, the transaction has no confirmed receipt. If it shows success or failure, the transaction has been included, even if the wallet display has not caught up.

Compare the transaction’s timestamp with the outage and the latest block. A slow page refresh is not evidence that the swap is still waiting. Refresh the explorer or query a trusted Base data source after blocks resume before deciding what to do next.

Has your account’s nonce moved?

The nonce is the next transaction number for a wallet on a network. Transactions from the same account use consecutive nonces, so a pending transaction can hold up later ones. Check the account’s confirmed transaction history and nonce on Base. If the nonce has advanced, look for the transaction that used it; a replacement or another transaction may already have been included.

Do not send the same swap again just because the wallet still says “pending.” A second transaction can create a second trade if both are eventually included. If you decide to replace a genuinely stuck transaction, use the same nonce and understand that the replacement may execute once the sequencer accepts it. A replacement is not a cancellation unless it is included first and consumes that nonce.

Did the swap execute against the pool?

After Base resumes, inspect the receipt and your token balances. A successful receipt means the transaction ran; it does not by itself prove the swap delivered the amount you expected. Check the transaction’s events or the resulting balances. A failed receipt means the transaction was included but reverted, so the swap did not complete.

• No hash: confirm whether the wallet submitted the transaction before trying again.
• Pending hash: wait for the chain and nonce checks; avoid duplicate trades.
• Successful receipt: verify the output tokens and amount.
• Failed receipt: inspect the failure before submitting a new swap.

The practical rule is simple: establish what happened to the signed transaction before making another one. The pool is touched at execution, not when a wallet first displays a pending swap.