> For the complete documentation index, see [llms.txt](https://arbydex.gitbook.io/arbydex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arbydex.gitbook.io/arbydex/arbydex-technology/transaction-monitoring.md).

# Transaction Monitoring

### Observing Every Execution

After execution, ARBYDEX continues monitoring the resulting blockchain transaction.

Transaction Monitoring provides visibility into the execution lifecycle.

#### Monitoring Flow

```
Transaction Submitted
        ↓
Blockchain Processing
        ↓
Transaction Confirmation
        ↓
Execution Result
        ↓
Recorded Activity
```

The monitoring layer can track relevant transaction information and execution status.

This creates a complete operational cycle:

{% code expandable="true" %}

```
Opportunity
     ↓
Analysis
     ↓
Validation
     ↓
Execution
     ↓
Monitoring
     ↓
Learning
```

{% endcode %}

Blockchain explorers and JSON RPC infrastructure provide the underlying mechanisms for interacting with and observing activity on BNB Smart Chain.


---

# 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://arbydex.gitbook.io/arbydex/arbydex-technology/transaction-monitoring.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.