Updated

MegaETH Daily Digest — May 16, 2026

Daily Transactions — 4 Weeks2.0M2.5M3.0M3.5M4.0MApr 18Apr 22Apr 26Apr 30May 4May 8May 12May 16
Daily Transactions — 4 Weeks
Unique Wallets — 4 Weeks010K20K30K40KApr 18Apr 22Apr 26Apr 30May 4May 8May 12May 16
Unique Wallets — 4 Weeks

At a Glance


Saturday activity cooled from Friday’s lift, but the network stayed comfortably busy for a weekend: steady baseline load, punctuated by a few short, intense bursts. With broader market conditions still cautious, the onchain mix skewed toward routine DeFi flows and automation rather than organic “exploration” traffic.

The Week So Far

MegaETH’s last two weeks have been defined by one extreme outlier and then a return to range. May 2 remains the standout at 46.6 average TPS (and a 220.8 TPS peak), while most subsequent days have settled into the high-20s to low-30s.

This week is modestly stronger than last week on throughput—30.2 TPS vs 28.7 TPS (+5.1%)—but the weekend profile has shifted: this weekend is tracking below last weekend’s pace (28.9 TPS vs 37.5%). On the adoption proxy, unique wallets have been choppier: after earlier spikes (notably 39.7K on Apr 30), May has mostly lived in the mid-to-high single-thousands, sliding into 6.3K on May 16.

TPS — Last 14 Days30354045May 2May 4May 6May 8May 10May 12May 14May 16
TPS — Last 14 Days

The Day

The cadence on May 16 was mostly flat, with a mild ramp into the early UTC morning and a gradual fade later in the day. Hourly averages stayed around the ~29–33 TPS band, but the day’s defining moments were brief: the network hit a 82.0 TPS peak at 07:13 UTC and an even more pronounced gas burst of 311.6 Mgas/s at 09:09 UTC—both flagged as extreme relative to the prior-day baseline.

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

App-wise, the top of the stack was tight but telling:

Two new contracts stood out for “startup burst” behavior:

For a quick “where did the chain feel hot?” scan around those spike windows, the Network Heatmap is the fastest way to pinpoint the exact minutes and clusters.

Top DApps — 24h TransactionsWorld Markets144.8KEuphoria143.0KFerdy.bet39.3KOffshore Protocol21.8KKumbaya6.7KPump Party5.8KCanonic1.2KgTrade | Gains Ne…1.2K
Top DApps — 24h Transactions

Health Check

At the network level, May 16 looked healthy: 0.2% failed transactions (5.5K failed out of 2.59M) is low and notably improved from Friday’s 0.8%.

The interesting health signals were localized:

The Takeaway

May 16 was a “stable weekend baseline” day—lower than Friday on TPS, transactions, and unique wallets, but still active, with short, sharp bursts likely driven by automated DeFi strategies (led by World Markets). Network-wide reliability was solid, and the few failure spikes look more like competition/automation dynamics than systemic issues.

On TGE tracking, the onchain activity doesn’t translate into a milestone shift yet: the Road to TGE remains at 6/10 LIVE MAFIA apps and shows $0.0M circulating USDm and $0K fees above the per-app threshold. The most relevant takeaway for watchers is simply that qualified-app activity (notably Kumbaya) is present, but it’s not yet expressing as fee generation or USDm circulation on the public tracker: 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-05-15