L2 transaction counts have surged, but the number of unique contracts hasn't moved. This likely means the same contract is being called repeatedly to inflate numbers, not that new applications or use cases are emerging. Looking only at transaction volume is like listening to noise. To confirm if activity is genuine, you need to compare three metrics separately: users, contracts, and gas consumption.
Step 1: Break Down Transaction Growth Structure – More Contracts or One Contract Spamming?
First, look at the source of transaction growth. If the number of unique contracts hasn't changed, the issue is nearly confirmed.
What to do: On Dune Analytics or the L2's official dashboard, pull up two charts: daily transaction count and daily number of unique contracts deployed.
How to do it: Compare the time-series curves. If transaction volume is rising while the unique contract curve stays flat or even declines, it means new transactions are concentrated in a few existing contracts. According to a widely used L2 growth evaluation framework, monthly active addresses growing without an increase in applications may indicate that only a few popular apps or spam/wash-trading activity is driving the data.
Completion standard: You've confirmed that new transactions are indeed concentrated in a few contracts rather than spread across many new ones.
Step 2: Break Down Transaction Sources – Real Users or a Few Addresses Spamming
High transaction volume without user growth is another classic sign of wash-trading.
What to do: Check the Daily Active Addresses (DAA) and Daily Transaction Users (DTU).
How to do it: If transaction count triples but DAA and DTU barely change, it means the same addresses are sending transactions repeatedly. Ideally, transaction volume and active addresses should grow together. If they diverge, it's likely scripts or bots at work.
Completion standard: You've confirmed whether active addresses and transaction volume trends are synchronized.
Common Mistakes
Focusing only on transaction volume rankings and thinking "high volume means the ecosystem is booming." Transaction volume can be artificially inflated at very low cost—especially since L2 gas fees have dropped to $0.004–$0.008, making wash-trading extremely cheap. Transaction volume alone cannot prove genuine activity; that's a basic rule of L2 data interpretation.
Step 3: Check Gas Consumption – Real Transactions Burn Money, Fake Ones Don't
This is the most decisive verification method. The goal of wash-trading is to create data cheaply, so they won't want to pay more gas.
What to do: On a block explorer or gas tracking panel, look at the L2's total gas consumption trend.
How to do it: If transaction volume spikes but total gas consumption barely changes or even drops, it means the new transactions are all extremely cheap "cheap transactions" with minimal gas cost—these don't execute complex logic, essentially taking up block space without doing real work. By contrast, real users calling DeFi contracts need more complex computations, leading to higher gas consumption.
Completion standard: You've confirmed gas consumption didn't grow with transaction volume, further proving the "lightweight" nature of the new transactions.
Faking L2 transaction data is simpler than you might think: deploy a contract and repeatedly call its own transfer function at very low cost, and the transaction count on dashboards can soar. For regular users, it's more important to look for qualitative signals like "are there new projects emerging on this L2?" or "is there community discussion?" rather than being swayed by explosive transaction numbers.
Verification Method After Completion
Open the L2 block explorer and randomly check 50 transactions from the days when volume spiked. If most are repetitive transfers from the same one or two addresses calling the same one or two contracts, then the conclusion that "activity is genuine" doesn't hold.
Next Steps
Add "unique contract count" and "active address count" to your L2 health monitoring checklist alongside transaction volume. If future transaction growth is accompanied by a rise in unique contract deployments, that signals the application layer is genuinely scaling – a sign worth paying attention to.
