Updated

MegaETH Weekly Report — Week 11 (Mar 9 – Mar 15, 2026)

MegaETH cooled modestly this week: 19.55M total transactions (vs 21.20M, -7.8%) alongside a much sharper contraction in participation, with 10.7K average daily unique wallets (vs 23.6K, -54.6%). Despite the softer top-line activity, throughput remained comfortably within the chain’s operating envelope, with a midweek spike to 161.1 peak TPS and no sustained reliability degradation. The week’s shape reads less like broad user expansion and more like activity concentrating into fewer, higher-intensity flows—consistent with cautious broader market conditions and a rotation toward “power user / bot-like” interaction patterns.

Daily Transactions — 4 Weeks2.0M2.5M3.0M3.5M4.0MFeb 16Feb 20Feb 24Feb 28Mar 4Mar 8Mar 12Mar 15
Daily Transactions — 4 Weeks

Network Activity

The week started with a participation-heavy Monday: 3.05M transactions paired with the week’s wallet peak at 37.3K unique wallets, but also elevated friction at 2.6% failed. Tuesday then became the clear volume high-water mark at 4.00M transactions (the busiest day), while unique wallets dropped to 6.2K—an early signal that the week’s incremental throughput was not being driven by broad-based user growth. This “high TX, low wallets” profile typically coincides with automated strategies, rapid-fire interactions, or concentrated liquidity/market-making loops rather than retail-style distribution.

Midweek (Wednesday) delivered the sharpest performance burst: peak TPS reached 161.1 and peak gas hit 19.9 Mgas/s, while the network-level failure rate improved meaningfully to 0.8%. That combination—higher instantaneous peaks with lower failure—suggests that the week’s most intense bursts were still absorbable without translating into widespread execution errors. After Wednesday, activity stepped down into a quieter regime: Thursday (2.56M) and Friday (2.23M) continued the downshift, and the weekend stabilized at the week’s floor of 2.03M/day (Saturday and Sunday), with failure rates compressing to 0.2% and 0.3% respectively.

Across the full arc, Week 11 looks like a “normalization” week after last week’s outsized wallet spike (73.7K peak). This week’s steadier baseline and lower wallet counts, combined with a mild rise in overall failure rate, points to transaction production concentrating in fewer hands rather than a network-wide demand shock.

DApp Leaderboard

At the app layer, the defining story was a reshuffling driven by a single standout gainer and two breakout movers from small bases.

  1. Kumbaya (miniblocks.io/dapps/kumbaya) took the weekly crown at 86.1K transactions, up from 44.6K (+93% WoW). That’s the largest absolute jump among labeled apps this week and a meaningful competitive step up. Its 20.4% failure rate is high in absolute terms, but the pattern is consistent with adversarial/competitive execution (e.g., race conditions, bot pressure) rather than necessarily degraded UX.

  2. The biggest “new momentum” move came from Avon (miniblocks.io/dapps/avon), which surged to 21.1K transactions from 2.0K (+959% WoW). Even with a relatively modest absolute count compared to top chain flows, this kind of order-of-magnitude expansion is the week’s clearest signal that users are rotating into lending-style activity. In a week where unique wallets fell sharply network-wide, Avon’s growth stands out as one of the few demand-positive app signals.

  3. TopStrike (miniblocks.io/dapps/topstrike) also broke out to 20.5K from 3.4K (+511% WoW), but with an unusually high 80.4% failure rate. This level of failed execution is commonly associated with highly competitive gameplay loops, scripted attempts, or throttling/guardrails—worth monitoring as “load shape,” not as a quality verdict.

On the downside, last week’s gaming leader Crossy Fluffle (miniblocks.io/dapps/crossy-fluffle) retreated to 34.7K (from 52.4K, -34%), and Ferdy.bet (miniblocks.io/dapps/ferdybet) softened to 25.9K (from 30.4K, -15%). Net-net, the labeled leaderboard reads like a rotation away from last week’s gaming intensity and toward a mix of DEX and lending, with a smaller but notable gaming rebound via TopStrike’s bursty (and failure-heavy) traffic.

For full coverage beyond the headline movers, the best view is the chain’s labeled ecosystem index on miniblocks.io/analytics.html, since much of the week’s transaction mass still sits outside the DApp registry.

Top DApps — 24h TransactionsKumbaya86.1KCrossy Fluffle34.7KFerdy.bet25.9KAvon21.1KTopStrike20.5KCanonic9.6KIntraverse7.1KMegaPunks5.4K
Top DApps — 24h Transactions

Notable Contracts

A large share of Week 11 throughput once again originated from high-volume contracts that are not in the DApp registry, and these contracts also explain a meaningful portion of the week’s failure profile.

MBIRD (0x0f5902d3f4e019dd83b4fa214d52c50308b1339e) dominated raw activity with 2.25M transactions and 161K failed. That single contract accounts for the majority of failed transactions observed in the notable-contracts set and is a strong candidate for why the network-level failure rate drifted up WoW even as weekend reliability looked clean. This is the week’s clearest example of “concentrated flow driving network texture.”

World Markets - Exchange (0x5e3ae52eba0f9740364bd5dd39738e1336086a8b) followed with 1.48M transactions and 32.5K failed—still large, but with a markedly lower absolute failed count than MBIRD, implying a different interaction profile (or less adversarial contention per call path).

OpenSea - SeaDrop (0x00005ea12886e54be34e2cc57d095c25e492f8ca) was small by volume (14.9K) but heavy by failure (12.2K failed). That “high fail-to-total” shape often lines up with mint/claim gating, bot contention, or precondition checks that intentionally reject most attempts.

Other notable unlabeled contracts (details via the Contracts Explorer):

Reliability & Health

From a network health standpoint, Week 11 was broadly stable, with a small WoW regression concentrated early in the week. Total failed transactions rose to 248K (from 234K, +6.0%), moving the aggregate failure rate to 1.3% (from 1.1%). The daily profile matters more than the weekly average: Monday and Tuesday were the stress points at 2.6% and 2.2% failed, after which the network settled into sub-1% territory for the remainder of the week (bottoming at 0.2% on Saturday).

This pattern—front-loaded failure that dissipates into the weekend—fits best with specific contracts/dapps producing adversarial contention (bots racing, limited-quantity conditions, or launch/mint mechanics) rather than systemic network instability. The DApp-level outliers reinforce that interpretation: TopStrike (miniblocks.io/dapps/topstrike) at 80.4% failed and Kumbaya (miniblocks.io/dapps/kumbaya) at 20.4% failed are consistent with competitive execution environments, not necessarily degraded base-layer performance.

Operationally, the key takeaway is that the chain handled a 4.00M-transaction day and a 161.1 TPS peak without a persistent failure spiral. The reliability question for next week is less “can the network handle it” and more “which specific flows are creating avoidable rejected-load.”

Failure Rate — Last 14 Days00.511.522.5Mar 9Mar 10Mar 11Mar 12Mar 13Mar 14Mar 15
Failure Rate — Last 14 Days

Market & Ecosystem Context

Broader market conditions remained risk-off throughout the week, and on-chain participation reflected that: unique wallets compressed materially WoW even as transaction throughput stayed relatively high via concentrated sources. That combination typically points to fewer discretionary users and a larger share of activity coming from automated strategies or tightly-looped power users.

Against that backdrop, the Road to TGE progress remains a meaningful lens for interpreting where activity is coming from and what might change next. MegaETH is currently at 5/10 “Live Mafia Apps” and the $500M USDM path sits at 12% progress. The per-app fee milestone remains far from the trigger condition this week (0 apps above $50K today; total fees today listed as $19K). The notable link to Week 11’s on-chain picture is that the week’s leading labeled DApp by transactions (Kumbaya) is also one of the tracked fee generators, but its current daily fees are still in the single-digit thousands rather than a breakout. Reference: https://www.megaeth.com/token.

Finally, while user counts fell, the ecosystem’s capital base did not show the same kind of contraction: TVL ended at $98.5M, up from $93.0M seven days prior (+5.9%). It’s not a large move in isolation, but in a week where unique wallets halved WoW, that mild TVL climb—paired with Avon’s lending activity surge—suggests capital is sticking even when participation is choppier.

Unique Wallets — 4 Weeks020K40K60K80KFeb 16Feb 20Feb 24Feb 28Mar 4Mar 8Mar 12Mar 15
Unique Wallets — 4 Weeks

Week Ahead

Watch whether Week 11’s “concentration” pattern persists: if transactions remain steady while unique wallets stay suppressed, activity is likely being carried by a small number of high-frequency contracts and competitive loops. On the app side, the key question is whether Avon’s and Kumbaya’s gains hold without pushing failure rates back into the early-week range. On the contract side, MBIRD and other high-reject flows should be monitored closely, since they are the most direct drivers of network-level failure variance.

Data sources: Analysis by MiniBlocks.io using on-chain MegaETH data. Market sentiment data from Alternative.me Crypto Fear & Greed Index. TVL and stablecoin data from DeFiLlama. TGE progress from megaeth.com.

Curious how this digest is made? Read about our AI-powered methodology.
This report is generated automatically by AI and may contain errors or inaccuracies. It is provided for informational purposes only and does not constitute financial, investment, or trading advice. MiniBlocks is an independent analytics platform and is not affiliated with, endorsed by, or promoting any project mentioned. Always verify data independently and do your own research.
About failure rates: This report covers raw network-level metrics. High failure rates for a contract or DApp do not necessarily indicate poor app quality. Common causes include bot activity (front-running, sniping), race conditions during launches and mints, intentional access gating, and rate-limiting mechanisms that deliberately reject excess transactions.
2026-W10