Self-Hosted Explorer Onboarding Guide

Self-hosting gives you a full OpenScan.AI explorer instance on your own infrastructure. Unlike the hosted explorer (which covers the supported public networks), a self-hosted instance is yours: your servers, your chain, your data.

Hosted ExplorerSelf-Hosted
SetupNoneClone and run from GitHub
ChainsXDC, EVS, Wanchain, VelasAny supported chain you configure
InfrastructureManaged by OpenScan.AIYour servers
Best forMost usersTeams wanting full control

Not sure which to use? See Choosing Your Explorer.

Step 1 — Get the Source

Clone the explorer from GitHub:

Terminal window
git clone https://github.com/OpenScanAI/<explorer-repo>

The OpenScanAI GitHub organization hosts the explorer stack and related tooling.

Step 2 — Configure Your Chain

Point the instance at your network:

  1. Set the chain’s RPC endpoint (an archive node is recommended for full history)
  2. Configure the chain ID, currency symbol, and network name
  3. Set your domain and branding options

💡 The indexer needs reliable access to a node for the chain you’re indexing. See Node Operators if you need to run one.

Step 3 — Run the Stack

Start the explorer services — the web frontend, the indexer, and the API:

  1. Review the setup guide for your environment in Setup & Installation
  2. Launch the services and let the indexer begin syncing
  3. Watch the sync progress until the indexer reaches the chain head

💡 Initial sync time depends on chain size and hardware. An SSD and a well-connected node make a big difference.

Step 4 — Verify and Launch

Once synced:

  1. Open your explorer’s URL and search for a recent block
  2. Check that transactions decode correctly
  3. Confirm the REST API v2 responds at /api/v2 (e.g. /api/v2/stats)
  4. Publish the URL to your community

💡 The same REST API v2 schema as the production explorer applies, so Blockscout-compatible tooling works against your instance.

Background & Further Reading