Base Denim Upgrade: What 200ms Blocks Change for Your Transactions
Base activated Denim on November 5, moving to 200ms canonical blocks and retiring Flashblocks. Here is what it means for users, builders and pending transactions.
Crypto Support & Research Desk
Quick answer: Base activated its Denim upgrade on mainnet on November 5, 2026 at 18:00 UTC. Blocks now arrive every 200 milliseconds instead of every two seconds, and the old Flashblocks preview feed is switched off. For most wallet users nothing needs to change, but apps, bots and contracts that count blocks as time may need updates.
What changed in the Denim upgrade
Denim is Base's fourth independent network upgrade, following Azul (May 28), Beryl (June 25) and Cobalt (September 30, 2026). It went live on the Base Sepolia testnet on October 21 and on Base mainnet on November 5 at 18:00 UTC, The Block reported.
The headline change is block time. Before Denim, Base produced one canonical block every two seconds. To make apps feel faster, it streamed "Flashblocks", previews of transactions every 200 milliseconds that were not yet part of a final block. Denim removes that preview layer and makes every 200-millisecond block a real canonical block, with its own hash, state root and receipts. According to Base's Denim overview, applications using Flashblocks have to move to standard block and RPC streams.
Denim also adds:
- BaseTime: a new predeploy contract that gives smart contracts access to time in milliseconds, plus millisecond-resolution timestamps in RPC responses.
- B20 token changes: new transfer protections and compliance controls for tokens built on Base's B20 standard. Transfers sent to a token's own contract address now revert instead of being lost.
What Denim does not do is raise Base's total capacity. It cuts latency, how quickly a transaction appears in a block, not the number of transactions the network can handle per second. Batching and gas sponsorship belong to a separate future upgrade called Everest, which has no activation date yet.
What it means for everyday users
If you use Base through the Coinbase app, the Base app or a common wallet, Denim should feel almost the same. Flashblocks already made confirmations feel near-instant, and now those fast confirmations are real blocks instead of previews.
You do not need to:
- Move or "migrate" your tokens.
- Claim anything or sign any upgrade transaction.
- Change your wallet address or reconnect your wallet.
One practical difference: block numbers now rise ten times faster. If you look up a transaction on an explorer, you will see far more blocks between two events than before. That is normal.
Who needs to act
Denim affects builders and some app users more than holders. You or the apps you use may be affected if they rely on:
- Flashblocks subscriptions. Base's migration guide maps
newFlashblockstonewHeadsandpendingLogstologs. Flashblocks WebSocket endpoints still accept connections but no longer send data, so a feed can look connected while delivering nothing. - The "pending" block tag. Base still accepts it, but it now returns the latest canonical block. There is no direct replacement for the old preconfirmation state.
- Block counts used as time. Timelocks, vesting schedules, cooldowns and voting windows measured in blocks now run ten times faster. For example, a one-hour cooldown set at 1,800 blocks would now expire in about six minutes. Base recommends using
block.timestampinstead. Contracts that cannot be changed may need a migration. - Node software. Base mainnet nodes needed to run base/base v1.5.1 or later and remove the old Flashblocks configuration flags.
Some projects built on top of Base were affected. Horizen said its OP Stack layer 3 network, which settles to Base, could not adapt and would stop accepting new user transactions shortly after Denim activated, with a deadline for bridging funds back to Base. If you used a network that settles to Base, check that project's official channels for any deadline.
Is Base running normally after Denim?
Yes. Base's status page confirmed at 18:14 UTC on November 5 that Denim had activated and said Base was investigating periodic transaction inclusion delays and a higher-than-expected number of empty blocks. The notice stayed in "Verifying" status for several days and was marked completed on November 9 at 19:45 UTC, when Base said all systems were stable after the upgrade. If a transaction seems stuck, check the Base status page before taking any action.
Base also explains how final a block is. A block becomes "safe" once its batch is posted to Ethereum, and "final" once Ethereum finalizes that batch. A fast 200-millisecond block confirms your transaction on Base quickly, but withdrawals back to Ethereum still follow Base's normal bridge rules.
How to check a Base transaction after Denim
Step 1: Find the transaction hash
Copy the transaction hash from your wallet's activity screen or from your Coinbase transaction details. If you sent funds from Coinbase to Base, our guide to checking a Coinbase to Base transfer shows where to find it.
Step 2: Look it up on a Base explorer
Paste the hash into a Base block explorer such as Basescan. A status of "Success" with a block number means the transaction is in a canonical block.
Step 3: Check the status page if it is pending
If the explorer cannot find the hash after a few minutes, check the Base status page for active incidents. Our guide to pending Coinbase transactions on Base walks through the next checks.
Step 4: Do not send it again
Sending the same payment twice will not speed up the first. If the first one later confirms, you will have paid twice.
Step 5: Check the bridge separately
If you were bridging, the Base side may be confirmed while the other chain is still processing. See our guide on tracking a pending bridge to Base.
What builders should do now
Base's checklist for developers is simple:
- Inventory every Flashblocks subscription, WebSocket connection and request that uses the "pending" tag.
- Find any code that reads
flashblock_indexor depends on preconfirmation state. - Search contracts and off-chain services for logic that converts block counts to time.
- Update node flags and client versions.
- Test migrated integrations on Base Sepolia or Base's Vibenet test environment before mainnet traffic.
Chainstack's Denim RPC guide gives a provider-side view of the same migration and notes that faster blocks can raise infrastructure costs.
How Denim compares with earlier upgrades
Cobalt, activated on September 30, focused on transaction controls and token-issuance tools. Our Cobalt user guide covers that change. Denim is a deeper change to how Base produces blocks, but like Cobalt it needs no action from ordinary token holders.
Frequently asked questions
Do I need to do anything with my tokens because of the Base Denim upgrade?
No. Denim changes how Base produces blocks. Your tokens, addresses and balances stay the same, and there is nothing to claim or migrate.
Why are Base block numbers so much higher now?
Base now produces a block every 200 milliseconds instead of every two seconds, so block numbers rise ten times faster than before.
What happened to Flashblocks?
Denim retired Flashblocks. Each 200-millisecond block is now a full canonical block, so the separate preview feed is no longer needed and stopped sending data.
Does Denim make Base cheaper or increase capacity?
Denim reduces latency, not throughput. Fees still depend on demand, and Denim does not raise the network's total capacity.
My Base transaction is pending after Denim. What should I check?
Look up the hash on a Base explorer, check the Base status page for incidents, and avoid sending the same transaction again.
Conclusion
Denim makes Base's fast confirmations real blocks instead of previews. For holders it is a background change with nothing to do. For builders, it is a migration: replace Flashblocks feeds, stop treating block counts as time, and test before you ship. If anyone asks you to "upgrade" your wallet for Denim, walk away.
This article is for general information only and is not financial, legal or investment advice. Base Coin Support is an independent publication and is not affiliated with Coinbase or Base. We will never ask for your recovery phrase, password 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 & 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.