Explorer views

Embed an individual Explorer view using the same emb_ key and allowed-domain settings as the map embed. The existing Explorer components provide balances, activity, transfers, charts, filters, pagination, and transaction previews where available for that view.

Quick start

<iframe
  title="Solana token explorer"
  src="https://www.scanner.net/embed/sol/token/So11111111111111111111111111111111111111112?embed=1&key=YOUR_API_KEY"
  width="100%"
  height="720"
  sandbox="allow-scripts allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  allow="clipboard-write"
  style="border: none; border-radius: 12px;"
></iframe>

Supported views

Use sol for Solana or rh for Robinhood Chain:

Append ?embed=1&key={API_KEY}. For Robinhood Chain, addresses and transaction hashes use their 0x form. For Solana, use the mint, wallet address, signature, or slot number.

You can also append ?embed=1&key={API_KEY} to a regular detail URL such as /rh/address/{ADDRESS}. It redirects to the corresponding /embed/rh/address/{ADDRESS} wrapper and preserves the query string. Regular detail pages without embed mode reject cross-origin framing.

Explorer homepages and Scanner account/tool pages are not embedded by this feature.

Navigation and view state

• Detail links and search results navigate inside the iframe and retain its key, including when changing chains.
• Tabs, filters, pagination, and browser history retain embed context. Existing view-specific query parameters continue to work.
• Links to the Explorer homepage, scanning tools, and account pages open a separate tab without passing the embed key. External links remain external.
• Site navigation, footer, and the personal pinboard are hidden. The Explorer search field and transaction previews remain available.

To switch the embedded view from your application, update the iframe's src:

function explorerEmbedUrl(chain, view, value, apiKey) {
  const params = new URLSearchParams({ embed: "1", key: apiKey });
  return `https://www.scanner.net/embed/${chain}/${view}/${encodeURIComponent(value)}?${params}`;
}

Access and limits

The server validates the embed key before rendering the view and applies the organization's frame-ancestors domain policy. Missing or invalid keys show an error instead of Explorer content; if validation is unavailable, the embed fails closed. Key-bearing page responses are private and not cached, while the underlying public Explorer data keeps its normal caching.

Explorer views use the existing public read APIs and their rate limits. Loading, filtering, or paging an Explorer view does not start a deep scan or spend map-scan credits. Map scans retain their separate usage limits.

See Authentication for domain registration and key validation, and Implementation guide for the host page's CSP and iframe sandbox settings.