> For the complete documentation index, see [llms.txt](https://wiki.shellprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.shellprotocol.io/user-guide/shellscan.md).

# Shellscan

## Explore with Shellscan <a href="#start-exploring-with-shellscan" id="start-exploring-with-shellscan"></a>

[Shellscan](https://app.shellprotocol.io/scan) is a user-friendly block explorer just for Shell Protocol transactions. It has its own tab, 'Scan', in the Shell App. [Click here to read more about Shellscan's backstory.](https://shellprotocol.io/posts/introducing-shellscan/)

With Shellscan, you can easily see every Shell transaction you’ve ever sent. You can even see a breakdown of the sub-transactions, giving you insight into the inner workings of the [Ocean](/how-shell-works/the-ocean-accounting-hub.md) and the [Shell primitives](/getting-started/integrations/shell-native-primitives.md) you’ve used. For example, you can now see the transaction path of a swap.

![](https://cdn-images-1.medium.com/max/3588/0*1ZdLKVQM3YYaET-s)

If all you’re looking for is a breakdown of your own account activity, Shellscan is much better than block explorers like Etherscan, which can be a bit overwhelming. If you do want to examine a Shell transaction on [Arbiscan](https://arbiscan.io/), just click the link on its transaction hash.

![](https://cdn-images-1.medium.com/max/7680/1*lZ-kWHiJZmPusMutilBelA.png)


---

# 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:

```
GET https://wiki.shellprotocol.io/user-guide/shellscan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.