> For the complete documentation index, see [llms.txt](https://docs.esprezzo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.esprezzo.io/introduction/smart-contract-visualization.md).

# Smart contract visualization

{% hint style="info" %}
**New**: Go beyond real-time alerts with data visualization for smart contracts.
{% endhint %}

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

Dispatch makes it easy to monitor patterns and visualize activity trends in smart contracts, with insights about function calls, event emissions, and active addresses (accounts/wallets) interacting with your contracts.

### Use visualization to identify

* Trending function calls and event emissions
* Top addresses interacting with the contract
* Activity trends over time

### Visualizing smart contract activity is as easy as

1. Adding a smart contract to Dispatch
2. Creating a Patch to monitor select activity (function calls and/or event emissions)
3. Looking at contract activity in Dispatch

We currently support monitoring of smart contracts on Arbitrum, Base, Ethereum, Optimism, and Polygon.

For more details, check out [Visualizing smart contract activity (Data viz)](/smart-contract-activity/visualizing-smart-contract-activity-data-vis.md)


---

# 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.esprezzo.io/introduction/smart-contract-visualization.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.