Practical overview
When it fits
Use the explorer for ADAMANT chain lookups and monitoring. For software integrations, the project directs developers to adamant-api-jsclient rather than treating the explorer’s UI routes as a general-purpose API.
Who it is for
- ADAMANT users checking a particular block, transaction, account or delegate.
- Readers monitoring delegate forging status, network peers or recent chain activity.
- Operators seeking the documented code and requirements to configure a self-hosted explorer.
Documented uses
- Search for ADAMANT blocks, transactions, accounts and delegates.
- View forging status for active and standby delegates.
- Inspect peer versions and heights and view peer locations on a map.
- Follow recent blocks and transactions through a live activity graph.
Requirements & limits
The repository documents a clear-web deployment at https://explorer.adamant.im and a Tor deployment. The service itself is a web interface; the repository also documents self-hosting.
- The public repository is licensed under GPL-3.0 and identifies JavaScript as its primary language.
- Self-hosting requires Node.js ^22.18.0 or >=24.11.0 and configuration of ADAMANT nodes.
- Redis is recommended but not required; without it, caching and persisted rolling block statistics are disabled.
- Peer geolocation is enabled by default and sends peer IP addresses to GeoJS and its infrastructure providers; operators can disable it while retaining peer listings.
- The explorer documents its HTTP routes as serving its own UI, and recommends adamant-api-jsclient for applications and integrations.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install and configure a self-hosted explorer
Prepare the explorer locally and configure it to connect to ADAMANT nodes.
Before you start
- Node.js ^22.18.0 or >=24.11.0
- Several independently operated ADAMANT nodes for the nodes_adm configuration
- Redis is recommended for API response caching and retaining rolling block statistics between restarts
Steps
Clone the repository and enter its directory.
Install dependencies and build with npm install and npm run build.
Copy config.default.jsonc to config.jsonc and configure nodes_adm with several independently operated ADAMANT nodes.
Prefer HTTPS node endpoints, then run npm start and open http://localhost:6040.
Expected outcome
The project documents a locally running explorer configured to check node health and fail over between configured nodes.
Guide limitations
- Without Redis, the explorer remains available but API response caching and persisted rolling block statistics are disabled.
- This setup guide does not cover public deployment, reverse-proxy configuration or PM2 process management.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 10 October 2026
- Original website title
- Adamant-im/adamant-explorer · Official homepage title · retained in its source language

