An OpenScan.AI deployment is a small set of cooperating services that turn raw chain data into a branded, AI-enhanced explorer.
Service Map
EVM Node ──► Indexing Engine ──► PostgreSQL ──► Backend/API ──► Frontend ──► Users ▲ Configuration Service (chain + branding settings)Indexing Engine
Connects to your chain’s EVM node via JSON-RPC and continuously fetches blocks, transactions, receipts, logs, and traces. It decodes token standards and contract calls, and writes normalized records to the database. Details: Indexing Engine.
PostgreSQL
The system of record for everything the explorer shows. Holds blocks, transactions, addresses, tokens, NFTs, and verified contract data. See Persistent Storage & Backups.
Backend / API Service
Serves the REST API v2 — the same API shape documented at xdcscan.io/api-docs — to both the frontend and external integrators. Details: Backend Service.
Frontend
The web UI users see: pages for blocks, transactions, addresses, tokens, and contracts, plus AI-generated summaries of on-chain activity. Rendered from API data and branded per chain.
Configuration Service
Loads chain parameters (chain ID, RPC endpoints, native coin symbol) and branding (name, logo, colors, domain) and distributes them to the other services. Details: Configuration Service.
Background Services
Housekeeping workers: statistics aggregation (daily transaction counts, gas trends), custom-domain routing, and periodic cleanup. Details: Background Services.
Deployment Models
- Hosted EaaS — OpenScan.AI runs all services; you get the branded explorer and API. See Hosted Onboarding.
- Self-hosted — you run the same services with Docker on your own hardware. See Setup & Installation.
Key Properties
- Chain-agnostic — works with any EVM-compatible network; production deployments include XDC Network, EVS, Wanchain, and Velas.
- API-first — everything the UI shows is available through the REST API.
- AI-enhanced — transaction summaries and contract explanations built on indexed data.