We would like to inform the community that TZStats, blockchain explorer maintained by Trilitech, will be decommissioned by February 18, 2026.
This decision is based on low usage and a limited number of visits over time.
What should users do?
We encourage all users to migrate to TzKT, which provides an actively maintained and feature-rich alternative.
Should you require assistance migrating from TZStats to TzKT, please contact the Trilitech or Nomadic Labs teams. We will provide the necessary information to support a smooth transition.
Your feedback matters
If you were using TZStats and relied on specific features that are not yet available elsewhere, we invite you to share your feedback here: Feedback | Tezos
This feedback will help us assess potential next steps and improvements in the Tezos tooling ecosystem.
Thank you for your understanding and continued support.
It was good to have two options to sanity check against each other. Right now TZStats is telling me I still own tokens which I transferred months ago and TzKT is not reporting transactions correctly.
If TzKT is going to be stabilized soon, I would perhaps feel more comfortable not being able to dual source data.
I was also working on a new project making good use of tzgo just this week. Is that going to be fine or do I need to wait another year before attempting to build anything here again? Because I don’t care too much about TZStats the UI, but their libraries are how I’m currently working around problems with TzKT.
Hello everyone,
Thank you all for your feedback and suggestions.
For clarification, I’d like to confirm that TzGo remains maintained. The decommissioning mentioned above applies only to tzstats.com.
As shown in the repository, TzGo supports Tallinn, and there are no plans to discontinue it.
I know we’re focusing on feedback to make sure we have our favorite features from TzStats on TzKT and migrating there but can we talk about the implications of this deprecation?
I know TzStats has not been in the finest shape for quite some time. We’ve had to explain to many people what was going on and why some data was not displaying properly and staking features were unavailable. From that perspective, it’s quite natural and unavoidable to have to pull the plug.
But what about the concept or having a decentralized chain relying on centralized infrastructure? This undermines the core value proposition.
We seem to be expanding in so many ways in terms of tools and services offered. If we were stagnating everywhere and everything was perishing and nothing new was being put out, removing TzStats would make sense but in our reality we’re actively choosing to go down to 1.
Baking Bad has been nothing short of stellar and exemplary over the years. Without them, we would be in such deep trouble. We’re now choosing to put even more burden on their shoulders.
Here are some some reasons I think having but 1 blockchain explorer is a bad idea.
One explorer going down shouldn’t take visibility of the chain with it
No second source to cross-verify means bugs, indexing errors, or flawed assumptions go undetected
Puts a lot of trust and influence in the hands of a single team that controls how data is presented and which metrics get highlighted
Fewer explorers means less competitive pressure to improve UX, add features, or keep pricing reasonable
Harder to independently verify governance votes, staking rewards, slashing events, and historical state
Developers get locked into one API’s quirks and roadmap with no fallback if priorities diverge or breaking changes happen
A decentralized chain relying on centralized infrastructure undermines the core value proposition
Bus factor risk if the remaining team loses funding, interest, or key personnel
A single entity is easier to pressure legally or regulatorily to censor, filter, or modify displayed data
Institutional knowledge disappears when an explorer shuts down, including how they indexed or interpreted certain edge cases
Potential developers and users may see a single explorer as a sign of an unhealthy or shrinking ecosystem
Without competition, API access costs can increase with no alternative for dependent projects
I always refer to tzstats when I wanna show “nerdy“ blockchain explorer but with pretty good visuals. Can I receive a code, maybe manual how to make my fezos node server to run my local (or even global) version of tzstats web?
What should users do?
