Run your own OpenScan.AI explorer instance from the open-source codebase at github.com/OpenScanAI.
Self-hosting gives you a private explorer for any EVM chain — a local devnet, a testnet, or your own production network — with the same UI and Blockscout-compatible API that powers xdcscan.io.
What you get
- The full explorer UI: blocks, transactions, addresses, tokens, verified contracts
- The REST API v2 on your own domain, with your own rate limits
- The indexer, continuously syncing your chain into PostgreSQL
- Account features: watchlists, private tags, API keys
System requirements
A minimal instance for a devnet or small testnet:
- 4 vCPU, 8 GB RAM, 200 GB SSD
- Docker 24+ with Docker Compose
- A synced JSON-RPC endpoint for your chain (archive node recommended for full history with internal transactions)
Production instances for busy chains should plan for 16+ GB RAM and fast NVMe storage — indexing is I/O-bound.
Architecture
| Component | Role |
|---|---|
| Indexer | Fetches blocks, txs, receipts, traces via JSON-RPC |
| API server | Serves /api/v2/... from indexed data |
| Frontend | The explorer web UI |
| PostgreSQL | Indexed data storage |
All components ship as containers; a single docker compose up runs the whole stack.
Documentation
- Installation — Docker, Compose, and source installs
- Configuration — environment variables reference
- Connecting to a Network — point your instance at a chain
- Production Deployment — TLS, reverse proxy, scaling
- Maintenance & Operations — upgrades, reindexing, backups
- Monitoring — health checks and metrics
- AI & MCP Integration — AI assistant access to your instance
- Operations Command Reference — day-to-day commands
Prefer managed?
If you’d rather not run infrastructure, Explorer-as-a-Service provides a hosted, branded OpenScan.AI explorer for your chain. For a quick local look, see Run a Local Instance.