How to Compare DeFi Dashboards Without Getting Lost
A practical guide to comparing dashboard fields, protocol labels, wallet data and update times.
This article may contain affiliate links. Commercial relationships are disclosed in the affiliate policy.
Two dashboards can show the same protocol and report different totals, and both can be correct. The difference usually comes from what each one counts, not from an error. Comparing them without a fixed order is how readers end up trusting whichever number they saw first.
Decide What You Are Measuring First
Before opening anything, write down the question. Total value locked, or value excluding a project’s own deposits? Assets under management, or assets held in the contract? Deposits, or borrows?
These are different quantities and dashboards choose differently. A number that answers your question on one dashboard may not be the same quantity on the next.
Total Value Locked Has Edges
The common headline figure counts assets deposited into a protocol’s smart contracts. The edges are where interpretations diverge.
Some dashboards subtract a project’s own deposits from the total. Some count tokens that were borrowed and redeposited elsewhere more than once. Some include a category of asset that another treats as off-chain or experimental.
When two dashboards disagree, this is the first place to look. A gap that disappears once you know both inclusion rules is explained. A gap that survives that is worth investigating further.
Check the Update Time, Not Just the Date
Most dashboards show when they last refreshed. Some update on a fixed schedule, some when someone triggers a rebuild, and some continuously per protocol.
A stale figure and a live figure for the same protocol are not comparable. Check the refresh indicator before comparing anything, and prefer the dashboard whose update cadence you can actually determine.
Protocol Names Are Labels, Not Identifiers
Dashboards label the same project differently, and occasionally list one project under two names. That splits a protocol’s total into two smaller numbers, which makes both look wrong.
Use the contract address as the stable identifier when a name looks unfamiliar. An address is unambiguous in a way that a display name is not.
Wallet Data Needs a Different Standard
A dashboard that shows wallet positions is aggregating many contracts, and each of them reports through its own interface. Balance errors, unusual token decimals and tokens with a transfer fee all show up here and nowhere else.
Treat per-wallet figures as approximate unless the dashboard documents how it handles those cases. A total that is off by a small percentage is normal in this category for reasons that have nothing to do with the protocol’s health.
A Repeatable Order of Operations
The same sequence, every time, removes most of the confusion.
- Write down the quantity you want and its exact definition.
- Pick the dashboard whose refresh cadence you can verify.
- Read its figure for the protocol, using the contract address to identify the protocol.
- Repeat on the second dashboard, checking its inclusion rules before comparing.
- Record both figures and the gap, with the rules that produced them.
Step five is what makes this useful later. A number without its inclusion rules cannot be re-checked, and a comparison you cannot repeat is not a comparison.
When a Disagreement Is Real
If the gap persists after accounting for inclusion rules, refresh timing and duplicate labels, then something operational is happening. A withdrawal that is large relative to the pool, a token that changed decimals, or a contract upgrade can all produce a genuine temporary divergence.
The habit that catches these is writing the comparison down. Most unexplained gaps become obvious once you can see them next to the date they appeared on.
This guide covers how to compare published figures. It does not assess any protocol’s safety or prospects, and a dashboard total is not evidence that the assets are safe or that the numbers will hold.