Failed Transactions
What it shows
Contracts attracting the most reverted transactions during the live window, with revert counts and the gas those failures wasted.
How to read it
Failed transactions still pay for the gas they consumed — failure has a price, and this widget shows who's paying it. A DEX router with steady reverts is normal (failed arbitrage, slippage protection firing). A single contract suddenly collecting dozens of reverts and millions in wasted gas usually means a misconfigured bot, a broken deployment, or users fighting over a popular mint. Labels and entity names make the culprit recognizable at a glance.
Data & update cadence
Rolling window of 3 epochs (~19 minutes), refreshed every block (~12 s).
Related pages
- Transaction Economics — failed fees in the per-block breakdown
- Transactions & Blocks — inspect an individual failure, including its trace