> For the complete documentation index, see [llms.txt](https://docs.blocktorch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blocktorch.xyz/concepts/data-sources/account-abstraction-modules/navigating-the-aa-explorer.md).

# Navigating the AA Explorer

#### 1. Have a transaction hash at hand to search for, or click on one of the auto detected transactions. Blocktorch's Account Abstraction is a multichain explorer.

<figure><img src="/files/XdikeDHHdw3HHzwaEA0Z" alt=""><figcaption></figcaption></figure>

#### 2. General transaction information

For each transaction the general transaction information include the Status, Timestamp, Gas Used, Gas Price, Fee and the Blunder Size indicating how many UserOps were bundled into this transaction

2.1 Successful Transaction

<figure><img src="/files/AStA7sNpx9DDGQbc8h1x" alt="" width="563"><figcaption></figcaption></figure>

2.2 Successful Transaction with internal failures

<figure><img src="/files/OlNu5GUbNnOSc0PPuEqw" alt="" width="563"><figcaption></figcaption></figure>

2.3 Reverted Transaction

<figure><img src="/files/IqZogO7KnKIPyLk3zyms" alt="" width="563"><figcaption></figcaption></figure>

#### 3. User Operation (UserOp) information includes Bundler Compensation, whether or not a new smart contract has been created in this transaction, if a paymaster was used, the amount processed by the paymaster and the user intent

<figure><img src="/files/Z47P7ZmLI9GqAQD23dFd" alt="" width="563"><figcaption></figcaption></figure>

Simply hover over the ℹ to learn more about each section.

<figure><img src="/files/FzQjHZPNFAen2v3WjAzj" alt=""><figcaption></figcaption></figure>

#### 4. The Anatomy of the full Account Abstraction transaction is visualized with the integrated providers of the modules tagged&#x20;

<figure><img src="/files/qC27HlESMS5L4sVDg48O" alt=""><figcaption></figcaption></figure>

#### 5. Function invocation call trace can be expanded to see the detailed invocation tree of the full trasnaction. The blue strips on the right side show the gas profiling, indicating which step used the most gas

<figure><img src="/files/aBbmEAZ01z7cfIEamBWh" alt=""><figcaption></figcaption></figure>

#### 6. Interactive interaction flow can be accessed by elapsing on the arrow on the right to see the full flow. The strength of the lines indicate the gas used on the transaction. The flow let's you follow were exactly the transaction failed. Clicking on the branches can elapse and expand the flow tree.

6.1 Successful Transaction

<figure><img src="/files/U5yxX1zy4Ku1oK9N3Qkh" alt=""><figcaption></figcaption></figure>

6.2 Successful Transaction with internal failures

<figure><img src="/files/dUOavroHEgo0tJM4mKw7" alt=""><figcaption></figcaption></figure>

6.3 Reverted Transaction

<figure><img src="/files/xA5Oua6kyHlM6spmF14t" alt=""><figcaption></figcaption></figure>

#### 6. Metrics are shown where available with KPIs about the Bundler, the Paymaster and the Smart Accounts used in the transaction

{% hint style="info" %}
Want to learn more about account abstraction and see blocktorch's AA explorer live in action? Check out this Workshop Series by [Alchemy](https://www.alchemy.com/) and [Offchain Labs](https://www.offchainlabs.com/) (Arbitrum):\
<https://www.youtube.com/watch?v=OglzIgPD-Zw>\
\[blocktorch's explorer live in action from minute 42:00]
{% endhint %}


---

# 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.blocktorch.xyz/concepts/data-sources/account-abstraction-modules/navigating-the-aa-explorer.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.