BASESUPPORT

Base Transaction Delays Resolved: What Happened After Denim and How to Fix Stuck Transactions

Base resolved its delayed transaction inclusion incident on 9 November 2026. Here is the timeline, what Denim's empty blocks and the v1.5.3 fix meant, and how to fix a stuck Base transaction.

Crypto Support Desk
Crypto Support Desk

Crypto Support & Research Desk

Published Nov 15, 2026
Updated Nov 15, 2026
7 min read
Referenced Assets:General Market
Share:

Quick answer: Base marked its "slower than usual transaction inclusion" incident on Base Mainnet as resolved on 9 November 2026 at 20:08 UTC, the same day it declared the Denim upgrade stable. Blocks were produced normally throughout and Base reported no lost funds. If a Base transaction still looks stuck, check its hash on a block explorer, then speed it up or resend from your wallet.

What happened on Base Mainnet

Base's official status page logged a degraded-performance incident at 13:36 UTC on 2 November 2026: "We are investigating reports of slower than usual transaction inclusion on Base Mainnet." Base added that "blocks continue to be produced normally" but that "some transactions may take longer than usual to appear in a block or preconfirmation."

The timeline from the status page:

  • 2 Nov, 13:36 UTC: investigating slow transaction inclusion.
  • 2 Nov, 14:36 UTC: "We've identified the performance degradation and have deployed optimizations."
  • 2 Nov, 14:55 UTC: a fix was implemented and Base began monitoring.
  • 9 Nov, 20:08 UTC: resolved. "Transaction inclusion is working as expected."

Base did not publish a detailed root cause beyond "performance degradation" and "optimizations", and it did not report any loss of funds. The incident also did not appear on Coinbase's own status page as an issue with Coinbase sends or receives on Base.

Earlier inclusion problems in late October

This was not the first such alert. Base logged an incident with the same wording on 29 October at 16:34 UTC, deployed a fix on 30 October at 19:28 UTC, and resolved it on 31 October at 16:37 UTC. On 24 October, a separate incident attributed to "unexpected mempool congestion" caused some transactions to be delayed or dropped from the mempool.

Denim, empty blocks and the state-root fix

The November incident overlapped with Base's Denim upgrade, which activated on 5 November 2026 at 18:00 UTC. According to the Denim upgrade incident page, Base reported at 18:14 UTC that "Denim has successfully activated" and that it was "investigating periodic transaction inclusion delays, causing a higher than expected rate of empty blocks." On 9 November at 19:45 UTC, Base posted: "All systems are stable following the Denim upgrade."

Earlier on 5 November, Base also disclosed a node software issue. A bug in Reth, the execution client Base builds on, discovered on 4 November, "could cause Base nodes to calculate an incorrect state root". Base said it had verified the current state root was correct and that users were not affected. It released node version v1.5.3 at 17:52 UTC and told operators to update, noting they did not need to resync.

What Denim changed for users

The Base blog post on Denim explains the main change. Base moved from one block every two seconds, with Flashblocks previews in between, to five full blocks per second, one every 200 milliseconds. Flashblocks was retired, so the "pending" tag no longer returns preconfirmed state.

Base also clarified finality. Inclusion in a 200ms block does not by itself make a transaction final. A block becomes "safe" once its batch is posted to Ethereum and "final" once Ethereum finalises it. Base said ordinary users did not need to take any action for the upgrade. Our Denim upgrade user guide covers the changes in more detail.

Who was affected

  • Wallet users may have seen transactions sit as "pending" longer than usual, especially on 2 November and in the hours after Denim activated on 5 November.
  • Traders and bots sending time-sensitive transactions may have seen slower inclusion or missed price windows.
  • App developers whose front ends relied on Flashblocks or the "pending" tag may have shown stale or confusing transaction states after Denim.
  • Node operators needed to run v1.5.1 for Denim and then v1.5.3 for the state-root fix.

As of 15 November, Base's status page shows all systems operational, including mainnet, testnet and both bridges, with no scheduled maintenance listed.

How to check a Base transaction that looks stuck

The steps below are general guidance for any slow Base transaction, not instructions from Base.

1. Find the transaction hash. Open your wallet's activity list and copy the hash for the transaction that looks stuck.

2. Search it on Basescan. If it shows as successful, the transfer is done and your wallet just needs to refresh. If it shows as failed, the funds did not move, although gas may have been spent.

3. If Basescan cannot find it, the transaction probably never reached the network or was dropped from the mempool. Your wallet may still show it as pending.

4. Speed up or cancel. Most wallets offer "Speed up" or "Cancel", which send a replacement with the same nonce and a higher fee. Use this rather than sending a brand-new transaction, which could result in paying twice.

5. Reset stuck nonces carefully. If several transactions are queued behind one that never landed, clear the first one before sending more. Some wallets have a "clear activity" or "reset account" option for this.

6. Refresh or reconnect the app. After Denim, some front ends needed updates to stop relying on the retired Flashblocks feed. Reloading the page or updating the wallet often fixes a display that looks stuck.

7. Check the status page. Before troubleshooting further, check status.base.org for any open incident.

What to avoid

  • Do not send the same payment again while the first one is still unresolved. Check Basescan first.
  • Do not approve unfamiliar contracts that claim to "unstick" transactions.
  • Do not treat a 200ms inclusion as final for high-value transfers. Wait for the transaction to reach "safe" or "final" status if the amount matters.
  • Do not rely on screenshots of status pages shared on social media. Go to the status page directly.

For more troubleshooting, see our guides on Coinbase Base transactions stuck pending and pending bridge transfers to Base.

What comes next

Base's next planned upgrade, Everest, is listed in its upgrade documentation as "planned for November 2026", with no confirmed activation date yet. We will publish a separate guide once a date is announced.

Frequently asked questions

Is Base Mainnet working normally now?

Yes. Base resolved the delayed transaction inclusion incident on 9 November 2026 at 20:08 UTC, and its status page showed all systems operational on 15 November.

Were any funds lost during the Base transaction delays?

Base did not report any lost funds. Blocks kept being produced throughout, and Base said users were not affected by the separate state-root bug fixed in v1.5.3.

Why does my Base transaction show as pending?

It may still be waiting for inclusion, may have been dropped, or your wallet may not have refreshed. Search the hash on Basescan, then use your wallet's speed-up or cancel option if needed.

What happened to Flashblocks on Base?

Flashblocks was retired when Denim activated on 5 November 2026. Base now produces full blocks every 200 milliseconds, and the pending tag no longer returns preconfirmed state.

Is a Base transaction final once it appears in a block?

Not by itself. A block becomes safe once its batch is posted to Ethereum and final once Ethereum finalises it.

Conclusion

Base's November inclusion delays are resolved, and the network has been stable since 9 November. If you still see a transaction stuck from that period, the fix is usually simple: look it up on Basescan, then speed it up, cancel it or let your wallet refresh. Rely on status.base.org for live information and never share your recovery phrase with anyone offering to help.

This article is for informational purposes only and is not financial or technical advice. Base Coin Support is an independent publication and is not affiliated with Base, Coinbase or any exchange. We will never ask for your seed phrase, private keys, passwords or 2FA codes.

Regulatory & Financial Risk Disclosure

The opinions, research, and analysis expressed in this publication are solely for educational and informational purposes and do not constitute investment, financial, legal, or tax advice. Digital asset markets are speculative and volatile. Past performance does not indicate future results. Always perform independent due diligence.

About the Author

Crypto Support Desk
Crypto Support Desk

Crypto Support & Research Desk

Crypto Support Desk publishes practical, source-led guides to exchange, wallet, network and on-chain service changes. Information is checked against primary or reputable security sources and is not investment advice.

Source-led crypto support research