Transparency Hub: dhbscan.com Launches for Contract Activity Tracking
By DeHub Team — 2025-04-03
In Q2 2025 we released dhbscan.com, letting users track activity across all DHB contracts.
Why a block explorer already exists and was not enough
Everything on dhbscan has always been public. It is on-chain. Anyone determined enough could find it.
That is the standard defence for not building something like this, and it is weak. "Technically available" and "practically checkable" are very different, and the gap between them is where opacity actually lives.
To verify DHB activity before this, you needed to know which contracts exist, across which chains, which addresses are ours and which are not, and what normal activity looks like. That is a research project. It filtered verification down to people with the time and expertise to do it — which is a small group, and not the group most exposed to being misled.
Publishing a policy and then requiring specialist knowledge to check compliance is only slightly better than not publishing it.
What it does
Collects DHB contract activity in one place, so a holder can see what is happening without first assembling a map of the ecosystem.
The design constraint was that it must not become a source of truth in its own right. dhbscan is a view over the chain, not a database of our claims about the chain. If it disagrees with the chain, the chain is right, and anything shown should be traceable back to the transaction it came from.
A "transparency" product that asks you to trust its own numbers has inverted its purpose.
Where this comes from
A direct line, and it starts with a failure.
In Q4 2021 our listing agent took the fundraise and dumped our chart. Gate investigated, apologised, and could not identify anyone because the records were lost. Our recourse ended at somebody else's missing paperwork.
Everything since has moved in one direction: provably fair draws, on-chain verified raffle mechanics, a published DEX policy, transparency reports, leaving centralised exchanges by choice.
dhbscan is that sequence finished. Not "we will tell you what we did", but "here is where you look".
The point of it
To make trusting us optional.
We would rather be checked than believed. Belief is fragile, it does not survive a bad quarter, and this project has had several. A verifiable record survives them, because it does not depend on anyone's opinion of us — including our own.
The uncomfortable consequence
It shows the bad periods too, and it cannot be configured not to.
Contract activity during the v2 migration, the aftermath of the listing agent incident, every treasury movement during quarters we would rather not revisit — all of it is visible, and none of it is annotated with our explanation.
That is the correct design. A transparency tool with a curation layer is a publishing platform, and the moment we could choose what it displays, it would stop answering the question it exists for.
The written accounts of those periods live in this archive, at full length, with the failures named. The tool shows the data. Keeping those two things separate is what makes either one worth anything.