> 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/understanding-transactions.md).

# Understanding Transactions

### Transparent Activity on BNB Smart Chain

ARBYDEX operates with on chain infrastructure on **BNB Smart Chain**, allowing supported blockchain transactions to be recorded and independently verified on the network.

Every confirmed on chain transaction receives a unique **Transaction Hash**, which can be used to inspect transaction details through a blockchain explorer such as BscScan.

On chain verification provides an additional layer of transparency because transaction information can be inspected independently from the ARBYDEX interface.

***

## Understanding Transactions

### What Is an On Chain Transaction?

An on chain transaction is an operation that is submitted to and processed by a blockchain network.

Within the ARBYDEX ecosystem, certain activities may result in blockchain transactions involving supported assets, wallet operations, or smart contract interactions.

A typical transaction lifecycle is:

{% code expandable="true" %}

```
Transaction Created
        ↓
Transaction Submitted
        ↓
Pending
        ↓
Blockchain Processing
        ↓
Confirmed
        ↓
Recorded On Chain
```

{% endcode %}

Once confirmed, the transaction becomes part of the blockchain's public record.

#### Platform Activity vs On Chain Transactions

Not every activity displayed inside the ARBYDEX platform necessarily represents a separate blockchain transaction.

For example:

**Platform Activity**

May include dashboard updates, node activity, internal balance movements, or other system events.

**On Chain Transaction**

Represents an operation that is actually submitted to the BNB Smart Chain network and recorded on chain.

This distinction is important when interpreting ARBYDEX dashboard metrics.


---

# 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/understanding-transactions.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.