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

# Transactions

This section shows the **latest transactions** on the blockchain. Alongside the table of recent transactions, you’ll see **statistics** and a **chart** of recent activity.

A **transaction** is the result of contract execution. Typically, a transaction is produced when an account processes one inbound [message](/use/messages.md) (external or internal) and it may emit zero or more outbound messages. Any user can send an **external message** (e.g., from a wallet or node) to call a contract.

### Statistics

At the top of the section is a block of statistics. \
The left side of the block displays transaction statistics: 

* **Total transactions**
* **Transactions per second**
* **Transactions (24h)**
* **Volume, 24h (EVER)** — total EVER value moved in transactions over the last day

The adjacent **chart** lets you visualize transaction dynamics over a selected time range.

![](/files/synQHdkS32GTZ7Xlj7F6)

### Transactions list

At the bottom of the page there is a block of the list of recent transactions.

Here are displayed:

* **Transaction ID** - unique transaction ID assigned when it is created
* **Transaction type** - ordinary or ticktock. Ticktock does not accept external incoming messages and can only be called from other contracts.
* **Exit code**
* **Method** - function name
* **Account** - address of the account that initiated the transaction
* **Balance change** - the number of EVER tokens debited or credited to the corresponding address
* **Time** - timestamp

Use the filters above the table (account, amount, time range, type) to narrow results.

Clicking a Transaction ID opens its [details](#transaction-details). Clicking an account opens that account in the [Accounts section](/use/accounts.md).

![](/files/VfvJfXsLaEz7uuOzyv2J)

## Transaction details

Clicking on the ID/Hash in any section of EVER Scan will take you to the details page for that transaction. The details page is divided into blocks: *Main Details, Token Transactions (if any), Messages, Payment, Storage, Credit, Computation, Action* and *Final State.* Below we look at each block in detail.

### Main details

Shows the core fields: **Hash (ID), Type, Method, Time (local & Unix), Account, Balance change, Value sent/received, Fees,** and the **block** where the transaction is included.

The **Decoded** **data** block (when available) appears here as well.

![](/files/y5VVXsz9mn0QhfBgz9ca)

### Token operations

Lists interactions with **non-EVER** **tokens** initiated by this transaction: **operation type, sender/recipient, token,** and **amount**. Each item links to the relevant detail pages.

### Messages

The ***Messages*** block contains a list of all [messages ](#messages)sent or received during this transaction. 

It shows the *Hash* of the message, the *Transaction* Initiator ID of the message, the [recipient and sender addresses](/use/accounts.md), the *method* and *value (EVER)* linked to the message.\
Clicking on one of these items will take you to its page in the corresponding section.

![](/files/SH7t9Je96jlgS5oIRt29)

### Fees

***Fees*** contains detailed information about the fees charged.

All "phases" of fees are displayed here in detail: storage fees, gas fees, etc.

{% hint style="info" %}
For fee formulas, see the Everscale docs on gas & fee calculation.
{% endhint %}

{% embed url="<https://docs.everscale.network/arch/managing-gas>" %}

![](/files/WeSXh3ZKwDp2ebb2UXTp)

### Phases

The storage, credit, compute, action, and final phases show the transaction’s execution stages:

**Storage phase** - collects payments for storing the account state.

**Credit phase** - credits EVER value from the inbound message to the account.

**Compute phase** - runs the contract code in TVM with the inbound message and constant data; produces exit code and a list of actions (e.g., outbound messages, deploy/activate).

**Action phase** - applies the produced actions. If actions cannot be completed, the transaction is aborted and state is rolled back.

**Final state** — summarizes whether the account was changed, destroyed, or left unchanged, and whether execution succeeded (exit code 0 or 1) or failed (non-zero/non-one).

![](/files/BPz5CGkUagM5vYvT9Cyg)

### Diagram

The **Diagram** tab visualizes the entire transaction cycle: which contracts exchanged messages, methods invoked, and which subsequent transactions were triggered.

Click **Graph** at the top of the block to open a larger view; switch between **Graph** / **Messages** / Transactions to explore the flow.

![](/files/d6D4gfypcd6jcmEYVKHV)


---

# 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:

```
GET https://docs.everscan.io/use/transactions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.