OpenScan.AI gives you three ways to explore on-chain data. Pick the one whose control model matches what you want.
| Hosted Explorer ↗ | Self-Hosted ↗ | Managed EaaS | |
|---|---|---|---|
| Setup | None — open the site | Clone from GitHub and run | Handled by OpenScan.AI |
| Chains | XDC, EVS, Wanchain, Velas | Any supported chain you point it at | Your chain |
| Branding | OpenScan.AI | Yours | Yours |
| Maintenance | None | You maintain it | Fully managed |
| Best for | Users and developers exploring supported chains | Teams wanting full control | Chains launching an official explorer |
| Open | xdcscan.io ↗ | github.com/OpenScanAI ↗ | Contact us ↗ |
Pick by audience
How much control do you need?
- None — just explore → xdcscan.io. Open the site and start searching. Begin with the Quick Start.
- Full control over infrastructure → Self-host from GitHub. Run the explorer on your own servers, pointed at your chain. See Setup & Installation.
- A production explorer for your chain, without the ops burden → Managed EaaS. OpenScan.AI deploys, hosts, and maintains a branded explorer for your network. Start at Explorer as a Service or contact the team.
For programmatic access — REST API v2, SDK, RPC-compatible endpoints — see the API Documentation.
What the hosted explorer looks like
Everything starts from the search bar:
- Search — paste a block number, transaction hash, address, or token name
- Transaction pages — AI-decoded summaries of what each transaction did
- Address pages — balances, token holdings, and full history
- Contract pages — verified source code with read/write interaction
For the full step-by-step, see the Explorer Onboarding Guide.
Background
The self-hosted and EaaS paths run the same explorer stack that powers xdcscan.io in production for XDC Network — including the Blockscout-compatible REST API v2 and RPC-compatible endpoints.