> For the complete documentation index, see [llms.txt](https://docs.thehemera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thehemera.com/welcome/account-centric-indexing-protocol/example-hemera-use-cases/socialscan-explorers.md).

# SocialScan Explorers

Blockchain explorer is an essential developer interface for every blockchain. To support a high performance blockchain explorer, a highly optimized indexing backend is needed to index on-chain transactions in near real-time, and service in particular account-level SQL queries efficiently. Also the indexing requires the coverage of full state and transaction history, along with essential data including trace, log, calldata (blob) etc. for each blockchain. Supporting blockchain explorer use case allows Hemera Network to: 1. provide 100% on-chain data coverage; 2. optimize its network performance.

On the other hand, the blockchain explorer space has been dominated by industry monopoly who charges as much as seven figures in US dollars annually (a whopping gross margin of 99% and higher!), hindering modular ecosystem development and further scaling solutions in the EVM space. 

Thus SocialScan Explorers, built on top of Hemera Protocol, provides the perfect showcase application  to bootstrap Hemera Network, all while resolving a major industry pain point.

To access examples of SocialScan explorers, see URLs below:

Manta Pacific: <https://manta.socialscan.io/>

Linea: <https://linea.socialscan.io/>

Taiko: <https://taikoscan.net/>

If you're a blockchain network interested in having your own SocialScan Explorer, reach out to us at <support@thehemera.com>&#x20;

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thehemera.com/welcome/account-centric-indexing-protocol/example-hemera-use-cases/socialscan-explorers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.