Make the explorer unmistakably yours.
Explorer-as-a-Service instances are themed per network. This page covers what can be customized and how to request changes.
What you can customize
Visual identity
| Item | Notes |
|---|---|
| Logo | Header and footer; SVG preferred, PNG accepted |
| Favicon | ICO or PNG, 32×32 minimum |
| Colors | Primary/accent palette; dark and light mode aware |
| Network name | Shown in the header, page titles, and meta tags |
| Currency symbol | Native coin symbol and name across all views |
Domain
- Use your own domain (
explorer.yourchain.org) via a CNAME record, or start on a subdomain of ours. - TLS certificates are provisioned and renewed automatically on managed domains.
Content and links
- Footer links: your site, docs, social channels, status page.
- Social preview images (the card shown when explorer links are shared).
- Faucet links for testnet instances.
- Gas tracker and price-chart visibility per network.
Feature toggles
- NFT views and metadata rendering
- Contract verification (UI and API)
- Account features: watchlists, private tags, API keys
- AI features: transaction summaries and natural-language search
- Advertising/announcement banner slots
Requesting changes
Branding is applied by the OpenScan.AI team as part of your managed service:
- Prepare assets: logo (SVG), favicon, brand colors (hex), footer link list.
- Submit them through your onboarding channel or support contact.
- Changes are staged on a preview environment for your approval, then promoted to production.
Typical turnaround for branding updates is a few business days; urgent changes (broken logo, wrong link) are prioritized.
Custom domains: DNS setup
Point your chosen hostname at the managed deployment:
CNAME explorer.yourchain.org → <provided-target>.openscan.aiOnce DNS propagates and TLS is issued, the instance answers on your domain. API consumers should use the custom domain too — https://explorer.yourchain.org/api/v2 — so links and integrations carry your brand.
API and tooling compatibility
Branding never changes API behavior: the instance stays Blockscout-compatible at /api/v2, and the interactive docs live at /api-docs on your domain. Wallets and developer tools that support custom Blockscout instances (including Hardhat and Foundry verification plugins) can point at your explorer with just a URL change — see the Verification Examples.