Independent DeFi security desk · Status: operationalMethodology & corrections · Submit an incident
DeFi Safety · Fact checked

How to Compare DeFi Dashboards Without Losing Context

Questions to ask about definitions, timestamps, chains and data sources.

This article may contain affiliate links. Commercial relationships are disclosed in the affiliate policy.

DeFi Safety — illustration keyed to this article's identifier. Source documents are listed under Sources and are not reproduced here.

Two dashboards can show the same protocol with very different numbers, and the gap between them is usually not an error in either one. It comes from choices each dashboard made about definitions, timestamps, chains and data sources before it drew anything. Comparing them well means recovering those choices, not picking the number you prefer.

Why Two Dashboards Disagree

Most DeFi dashboards answer slightly different questions.

One reports total value locked as of the last block it indexed. Another reports the same figure as of a fixed hour, rounded, from a data provider rather than from the chain itself. A third adds tokens that the first excludes because it only counts assets it can verify. None of them is lying, and all three produce a defensible number.

The disagreement becomes a problem only when you carry one figure into a sentence about the other. A protocol described as holding a billion dollars on one screen and eight hundred million on the next is not a contradiction you need to resolve. It is two measurement scopes that were never the same measurement.

The Four Questions

Before comparing any two figures, get a written answer to these.

  • What is being measured. Value locked, net deposits, trading volume, fees, revenue and active users are six different quantities that dashboards often label with similar words in list views.
  • Which chains are counted. A figure that includes nine layer 2 networks and a figure counted on one network alone are not variations of the same number.
  • What timestamp applies. Block height, block time, hourly average and daily snapshot respond differently to a volatile day.
  • Where the data came from. Reading directly from chain events, using an indexer, or calling a provider API introduces different amounts of delay and different handling of deprecated contracts.

Reading the Timestamp Before the Number

The timestamp is the fastest way to explain a gap, so check it first.

Block-indexed figures move in steps and can lag by a few blocks during heavy activity. Hourly averages smooth the same activity into a shape that never existed at any single moment. Daily snapshots discard everything that happened inside the day. Comparing an average against a snapshot produces a difference that looks like a data problem and is actually a method difference.

Record the timestamp with the number. A figure without a time attached cannot be checked by anyone later, including you.

What to Do With Two Numbers

If the two figures disagree and you cannot resolve why, report both with their timestamps and their scopes rather than choosing one.

For internal decisions the gap itself is often the useful signal. A large difference between a block figure and an hourly average means real movement inside the window. A large difference between two chain-inclusive figures points at a token classification difference. A difference that appears only on one provider suggests you are looking at an indexing delay.

For anything published, cite the figure with the source and the timestamp attached, because a dashboard total without them is not a fact anyone can verify.

Signs the Comparison Itself Is Broken

  • One figure has no visible timestamp, no chain list and no data source, and the page offers no way to inspect them.
  • A dashboard mixes value locked with total supply or with market capitalisation in the same visual.
  • A chain appears in one figure and is absent from another without being named.
  • The number changes noticeably when the page is reloaded, which points to a live or partially loaded query rather than a recorded figure.
  • The comparison was taken from a screenshot rather than the live page, so the timestamp is whatever moment the screenshot was taken.

Recording the Comparison

Write down both dashboard names, both figures, both timestamps, the chains each includes and the date you made the comparison. Dashboard definitions get revised, and a note that omits the date cannot be checked later.

Also record what you concluded. Most disagreements are method differences, and writing that down is what stops the same comparison from being re-argued every quarter.

What This Does Not Solve

Comparing definitions and timestamps tells you whether two figures are describing the same thing. It does not tell you which figure is more accurate, and it does not make any protocol safer.

It also says nothing about contract correctness, admin control or liquidity depth. A dashboard that measures a concept cleanly can still be reporting on a mechanism that does not behave the way the measurement assumes.

Sources and Limits

This article is educational and does not constitute financial, legal, tax or security advice. Dashboard definitions, coverage and indexer behaviour change without notice, so confirm the current state at the primary source before acting on any figure recorded here.

Sources