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

# Transactions

📡 **Transactions**

The **Transactions** section is your real-time stream of on-chain activity for all wallets added to this specific RayBot.\
Every buy, sell, swap, send, or contract interaction appears instantly — without delays or Telegram limitations.

#### Here you can:

⚡ **View all transactions in real time**\
Events appear immediately after they occur — with no queues or lag.

🎯 **Use advanced filters**\
Filter activity by:

* **Type:** Buy / Sell / Swap / Send / Other
* **Wallet:** display transactions from a specific wallet
* **Token:** filter by address, ticker, or tokens you've added earlier
* **Chain:** Solana / EVM / Tron
* **Date:** From / To ranges for deep analysis

🔍 **Analyze behavior of any wallet or token**\
See what was bought, sold, or interacted with.

📊 **Understand market context**\
Check essential token metrics and open charts in one click.

🔗 **Jump to blockchain explorers**\
Every wallet, token, and transaction includes a direct link for detailed inspection.

⚙️ **Customize your view**\
Sort by time, amount, token, chain, or transaction type.

> *🎥 Video example — Full walkthrough of the Transactions dashboard in under 2 minutes*

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/dkd80z8u9r>" %}

***

#### Why this section matters

**Transactions** shows the actions of tracked wallets in real time.\
Use it for monitoring KOLs, analyzing traders, or watching market flow as it happens.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.raybot.app/start/web-app/web/transactions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.