Updated

MegaETH Daily Digest — March 10, 2026

Daily Transactions — 4 Weeks2.0M2.5M3.0M3.5M4.0MFeb 10Feb 14Feb 18Feb 22Feb 26Mar 2Mar 6Mar 10
Daily Transactions — 4 Weeks
Unique Wallets — 4 Weeks020K40K60K80KFeb 10Feb 14Feb 18Feb 22Feb 26Mar 2Mar 6Mar 10
Unique Wallets — 4 Weeks

At a Glance


MegaETH stayed in a higher-activity regime on March 10, extending the step-up that started late last week. Even with broader market conditions still risk-off, onchain throughput hit a fresh 14-day high—though the day’s volume was unusually concentrated into a small number of wallets.

The Week So Far

This week is running hotter than last: 40.0 TPS average versus 30.5 TPS last week (+31.2%). The bigger story is the shape of activity—March 6–10 brought sustained higher baselines (47–48 TPS days) plus sharp, event-like spikes (including March 8’s 175.7 peak TPS and March 10’s new high).

TPS — Last 14 Days3035404550Feb 24Feb 26Feb 28Mar 2Mar 4Mar 6Mar 8Mar 10
TPS — Last 14 Days

Transactions have followed the same “higher floor” pattern. After March 5’s 2.65M TX, the network pushed to 4.06M on March 6 and held elevated volume through March 8–10 (3.05M–4.00M). Unique wallets, however, have been volatile: 73.7K on March 8, 37.3K on March 9, then down to 6.2K on March 10—an extreme swing that strongly suggests automation-heavy traffic (and/or uneven distribution of activity across a small set of actors) rather than a broad-based user drop.

Failure rates have been comparatively calm in the past week (0.6%–2.6% most days), a meaningful improvement from the late-February days where overall fail% briefly pushed into double digits (and one day much higher). March 10’s 2.2% sits squarely in the “nothing alarming” range at the network level.

The Day

March 10 had a “quiet-to-busy” rhythm with two distinct gears. Early hours sat mostly in the high-20s TPS (00:00–06:00 UTC), then the day repeatedly snapped upward—first around 07:00–11:00 UTC (40–65 TPS), and then a decisive late-afternoon surge where the hourly peak hit 103.6 TPS at 16:00 UTC (15.0 Mgas/s), staying very elevated at 17:00 UTC (98.0 TPS).

TPS — Today Hourly2040608010000:0003:0006:0009:0012:0015:0018:0021:0022:00
TPS — Today Hourly

Underneath the hourly curve were even sharper microbursts: the network TPS briefly spiked to 1,507 TPS at 12:20 UTC, and gas spiked to 569.4 Mgas/s at 01:42 UTC. Those are “burst events,” not the sustained baseline—and they line up with concentrated contract-driven activity.

On the application side, Kumbaya was the clearest “real users + real volume” leader: 11.8K transactions, 3,310 Mgas, and 2009 unique callers. Avon also stood out for breadth, with 1.4K transactions from 756 callers—consistent with the week’s broader trend of DeFi activity staying resilient even in cautious market conditions.

Gaming and high-frequency patterns were more uneven. Crossy Fluffle posted 7.5K transactions but only 29 unique callers, and also logged a single-hour spike of 4,161 tx/h around 02:00 UTC—highly suggestive of scripted play or automation bursts rather than organic session growth. Ferdy.bet contributed meaningful gas (1,554 Mgas across 4.0K txs), but with a smaller caller set (151), it read more like concentrated power users than a broad funnel.

Top DApps — 24h TransactionsKumbaya11.8KCrossy Fluffle7.5KFerdy.bet4.0KCanonic1.5KAvon1.4KMegaPunks511TopStrike503Smasher452
Top DApps — 24h Transactions

The contract-level story was dominated by two themes:

Finally, new contracts continued to be a meaningful share of throughput. The most notable was 0x9c04683a5cf877db60c7b4589f91d6de93f9418e (first seen ~21.7h ago): 7,787 transactions from 31 callers (251 tx/caller) and still active—again reading as automation-forward behavior. You can inspect it directly here: 0x9c04683a5cf877db60c7b4589f91d6de93f9418e.

Health Check

Network-wide health was fine: 2.2% failures on 4.00M transactions is not elevated for a high-throughput day.

The main reliability signal was localized. MBIRD saw a sharp failure spike around 11:00 UTC: 31,478 of 60,667 transactions failed (51.9%). Given MBIRD’s concurrent volume bursts, this is consistent with bot competition, race conditions, or deliberate reverts under specific conditions—not necessarily “something broken,” but it does explain why March 10’s headline throughput didn’t translate into broad wallet participation.

New, automation-heavy contracts also showed non-trivial failure rates (including 11% on the new contract linked above), which fits the same “high-frequency attempts” profile.

The Takeaway

March 10 was the busiest day in the past two weeks by sustained TPS (47.2) and it also featured extreme, contract-driven microbursts—high capacity, but concentrated. The big watch item isn’t network stability (overall fail% stayed normal); it’s the composition of demand: 4.00M transactions paired with just 6.2K unique wallets is a clear sign that automation dominated the day’s volume.

On the Road to TGE, the picture remains steady rather than accelerating: Live Mafia Apps stayed at 5/10, and no app cleared the $50K/day fee threshold (Kumbaya posted $16K; total fees across all apps were $28K). If this week’s higher-throughput baseline persists, the next meaningful milestone will likely come from sustained per-app fee streaks rather than one-off burst days. More context: https://www.megaeth.com/token

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-03-09 2026-03-11