I just wanted to formally and properly introduce Namadata.xyz - Namadata has been built by myself in partnership with the Kleomedes team.
Our primary contribution is our Statistics and Performance Monitoring Suite - available at Namadata.xyz.
The suite is powered by:
Namadata Daemon - A robust daemon indexing the Namada blockchain data and writing to our back-end DB’s
Namadata Web UI - A comprehensive web interface for monitoring and analyzing the Namada blockchain network.
Namadata API - Public RESTful API endpoints that power the Namadata web interface, providing access to processed blockchain data and analytics with historical tracking capabilities.
We are currently supporting the following monitoring:
Services Health Monitoring: Tracks the status and performance of all Namada blockchain services, including explorers, interfaces, indexers, and RPC endpoints. We provide health status, versioning, response times, and uptime metrics at 10 minute check intervals. We source our service providers from the Luminara registry.
Validator Analytics: Provides detailed validator information including consensus status, stake amounts, commission rates, and all-time uptime performance. Future support for notification system.
Network Metrics: Tracks key network metrics like total NAM staked , voting power distribution, average commission rates and real-time block production analytics.
Network Health Analysis: Monitors blockchain performance with metrics like average block time, min/max block times, and visualizations of block production over time to identify network anomalies.
Our API’s are all public - so anyone can consume our data.
We are continuing to build out Namadata to support IBC properly as well.
We aim to provide a data-rich experience for users and teams working on Namada and we also aim to improve developer tooling to allow others to build tools and dashboards.
We welcome any feedback or feature requests - we’re here to contribute in a meaningful way towards Namada.
We will continue to update here as we roll out additional features.
We also provide a number of open source contributions and tooling:
indexer-proxy - load balancer for indexer - one URL to automatically route between healthy indexer instances to ensure continuous data reliability rpc-proxy - load balancer for RPC - one URL to automatically route between healthy RPC instances to ensure continuous data reliability namada-rest-api - RESTful API exposing core Namada SDK data without requiring Rust/CLI
These past two weeks have made it clear that not all infra services are equal to the challenge of even small volume Namada use.
This should be VERY useful for Luminara and anyone else championing PGF for community infra providers, and similarly valuable for anyone promoting/recommending/using community infrastructure services. We’d be happy to support this.
Thank you for your support and feedback - we really appreciate it from yourself as well as everyone else that we’ve spoken to who has been able to help and guide us along the way.
We are really looking forward to bringing value now and into the future for Namada and especially for all of the stakeholders in the ecosystem - so we are 100% open to any feedback or feature recommendations.
To this end, we’ve just completed the first iteration of our IBC data which is live now at:
It’s still only early, but with phase 5 online we’re keen to continue to build it out and get the data and insights out there!
Just wanted to bang in a quick update before the weekend.
The IBC page is looking about 100x more polished now than it was before.
There’s only an issue with handling decimals on NAM gas which I’ll have to fix on the daemon.
The public API is fully online too and can serve any data needed - i.e IBC transactions by tx hash.
I just wanted to enquire about whether there was any interest for an IBC explorer?
I’m currently collecting all of the data, just not displaying it anywhere useful.
Any other IBC related data that people would like access to?
Having another 
is not only fun, its very useful.