> For the complete documentation index, see [llms.txt](https://docs.blocksec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blocksec.com/phalcon/phalcon-explorer.md).

# Phalcon Explorer

[**Phalcon Explorer**](https://blocksec.com/explorer) is a powerful transaction explorer designed for the DeFi community. It provides comprehensive data on *invocation flow, source code, balance changes, transaction fund flows, gas profiler, and state changes*. It also supports transaction debugging and transaction simulation. This tool aims to help developers, security researchers, and traders intuitively understand transactions.&#x20;

{% hint style="info" %}
**Visit the user manual for instructions on how to use Phalcon Explorer.**
{% endhint %}

## Supported Chains

* Mainnet: [Ethereum](https://ethereum.org/en/), [Solana](https://solana.com/), [Binance Smart Chain](https://www.bnbchain.org/en), [Arbitrum](https://arbitrum.io/), [Base](https://base.org/), [Polygon](https://polygon.technology/), [Avalanche](https://www.avax.network/), [Optimism](https://www.optimism.io/), [Mantle](https://www.mantle.xyz/), [MegaETH](https://www.megaeth.com/), [Monad](https://www.monad.xyz/), [Plasma](https://www.plasma.to/), [Story](https://docs.story.foundation/introduction), [Linea](https://linea.build/), [Gnosis](https://www.gnosischain.com/), [Scroll](https://scroll.io/), [HyperEVM](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm)&#x20;
* Testnet: [Story Aeneid](https://docs.story.foundation/network/connect/aeneid), [Sepolia](https://sepolia.etherscan.io/), [Hoodi](https://hoodi.etherscan.io/)

## Feedback

We value your input and would greatly appreciate any feedback or suggestions you may have.&#x20;

{% hint style="info" %}
Please use [the link](https://github.com/blocksecteam/Phalcon/issues/new/choose) to submit any feature requests or report any issues.
{% endhint %}

## Blogs

Here is a list of blogs on how to use Phalcon Explorer

* [Beyond 7 Days: Exploring the Endless Possibilities of Phalcon](https://blocksec.com/blog/beyond-7-days-exploring-the-endless-possibilities-of-phalcon-beyond-7-days-exploring-the-endless-possibilities-of-phalcon)[ Explorer](https://blocksec.com/blog/beyond-7-days-exploring-the-endless-possibilities-of-phalcon-beyond-7-days-exploring-the-endless-possibilities-of-phalcon)
* [How to use Phalcon Explorer Debugger to dive into a transaction ](https://blocksec.com/blog/how-to-use-phalcon-debug-to-dive-into-a-transaction-1)

{% hint style="info" %}
Please use [the link](https://github.com/blocksecteam/Phalcon/issues/new/choose) to submit any feature requests or report any issues.
{% 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.blocksec.com/phalcon/phalcon-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.
