Reference for the administrative surface of a hosted explorer.
Most operations on an EaaS instance are performed by the OpenScan.AI team on your behalf. This page documents what exists, what you can do yourself, and what to request.
Self-service operations
Things your team can do any time without a ticket:
API keys
Create and revoke instance-level API keys for your own tooling from the account page. Keys raise rate limits; they don’t grant admin powers. See API Keys & Rate Limits.
Health and status checks
# Indexing healthcurl https://explorer.yourchain.org/api/v2/main-page/indexing-status
# Chain stats (liveness)curl https://explorer.yourchain.org/api/v2/stats
# Interactive API docsopen https://explorer.yourchain.org/api-docsWatchlists and monitoring
Use account watchlists with webhooks to monitor network-critical addresses (bridge contracts, sequencer/foundation wallets). See Alerts & Webhooks.
Request-based operations
Submit through your support channel; typical turnaround is a few business days.
| Operation | What to provide |
|---|---|
| Branding update | New assets per Branding |
| Domain change | New hostname + DNS control |
| Token list curation | Contract addresses, icons, project URLs |
| Scam/abuse flag | Contract address + evidence |
| Feature toggle | Which feature, desired state |
| Usage report | Time range, metrics of interest |
| Rate-limit adjustment | Expected traffic profile |
Emergency operations
For urgent issues — explorer down during your launch, a scam token trending on your network, a security incident:
- Contact your dedicated support channel immediately (response times per your service agreement).
- Include: what you observe, when it started, and impact.
- For chain-side incidents (halted chain, consensus issues), the explorer reflects chain state — coordinate with your validator/node operators first.
Data retention and export
- Full indexed history is retained for the life of the service.
- Bulk exports (e.g. full transaction history for analytics) can be arranged as a one-off or recurring job through support.
- If you ever migrate off the service, a final database export can be provided to bootstrap a self-hosted instance.
Compliance and access control
For private deployments:
- UI and API access can be restricted by VPN, IP allowlist, or SSO — configured during onboarding.
- Audit logs of administrative actions are available on request.
Change management
- Managed upgrades are applied continuously; breaking changes are announced in advance.
- Your changes (branding, domains, toggles) are staged on a preview environment for approval before production.
- Incident history for your instance is available through your support channel.
Related
- Managing Your Explorer — the workflows behind these operations
- Supported Networks
- Self-Hosting — if you outgrow the managed model