If L2 sequencer revenue suddenly drops, first check the fee side (income), not the blob cost side (expenses). Lower blob costs can improve profit margins, but a drop in income usually happens because the sequencer collects less gas fees from users, not because it pays more to Ethereum. Also, blob fees and sequencer revenue are not directly linked—a "near-zero" blob market actually means L2 profit margins on data availability are bigger than many think.
Step 1: Check the sequencer's revenue (fee side)—did it really go down?
The sequencer's net revenue formula is: L2 transaction fees – L1 data availability costs – operating costs. A drop is easiest to spot as "less money coming in."
What to do: Check the recent sequencer revenue of your L2 on Dune Analytics or other on-chain dashboards.
How to do it: Find revenue dashboards for Arbitrum, Base, or Optimism. Compare daily average revenue for the last 30 days and the last 7 days. In early 2026, with ample blob space, median user costs on Base and Arbitrum fell to $0.004–$0.008. If average gas fees haven't bounced back and transaction volume hasn't grown much, revenue will decline.
Done when: You confirm that sequencer revenue has indeed fallen compared to earlier periods and rule out changes to the fee structure by the project team.
Step 2: Check blob costs (expense side)—are they really hitting net income?
Blob fees are a separate "data posting" cost, controlled by EIP-4844's independent blob fee market. Since the Dencun upgrade, blob fees often sit close to $0.
What to do: Look at the total blob fees that L2 paid to Ethereum over the relevant period.
How to do it: Data from Coin Metrics shows median blob fees have fallen to about $0.0000000005. Unless a short-term hype like "Blobscriptions" drives heavy data blasting, blob costs are nearly negligible. This means the cost L2s pay to Ethereum is a tiny slice of total revenue (sometimes under 2%), not "suddenly spiking higher."
Done when: You verify that the L2's DA costs haven't jumped abnormally, so the core reason for the revenue drop is not blob fees.
Step 3: Check whether a fee-sharing protocol is active
Some L2s have started sharing part of sequencer revenue with on-chain DApp developers (e.g., Blast, Mode). This changes the sequencer's own income structure.
What to do: Check if the L2 has a "sequencer fee sharing" or "gas rebate" program running.
How to do it: Read the L2's official docs or developer announcements. If the revenue drop lines up with the launch of such a program, it's likely because money meant to be shared is being paid out, not because activity is shrinking.
Done when: You find out whether the revenue drop is tied to a protocol-level income redistribution. If so, it's a normal economic adjustment.
A drop in sequencer revenue doesn't hit ordinary users as directly as a falling L2 token price, but if the project's earnings outlook keeps worsening, the team might balance the books by raising L2 gas prices, cutting developer grants, or even delaying sequencer decentralization. Check the L2's public dashboard (like a sequencer profit panel on Dune) regularly rather than judging from one transaction fee.
How to verify your analysis
Use Dune or Nansen to check the L2's "daily active addresses" and "daily transactions" over the past 30 days. If revenue is down but transactions are up, the L2 is earning through high volume and low margins. If revenue drops while transactions also fall, ecosystem activity is cooling—then look at the L2's developer incentives to see if new application-layer opportunities might appear.
Next steps to take
If you've deployed an app or provide liquidity on this L2, add "sequencer revenue changes" to your on-chain monitoring list. Persistently low revenue could soon affect grant support for ecosystem projects; longer-term, the L2 may be forced to adjust its fee model. Watch the official governance forum for any proposals.
