# Unified Transaction List

In this page you can browse all the tx happening on Avalanche. Whether you are new to Avascan or an experienced user, this guide will provide you with the knowledge and tools to understand and navigate transactions effectively.

### Page structure

This page is accessible by clicking from the homepace on **Blockchain** and then **Transactions**. 

Each type of data has a different tab and you can easily switch betweeen them.

<figure><img src="/files/28qzuDadJ8eWAEckqtWW" alt=""><figcaption></figcaption></figure>

### Transactions

<figure><img src="/files/Y8j1MJfyX78zCt3FDBTA" alt=""><figcaption></figcaption></figure>

In this section you can browse the latest transactions happening inside and outside the Avalanche network system.

The results are displayed in different columns:&#x20;

* **Hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed
* **Method, if applicable:** the main contract method used in the transaction.
* **Block Info:** the number of the block and the date and hour when the transaction occurred
* **From:** sending address
* **To:** receiving address
* **Value & Fees:** the token and the quantity involved and the fees of the transaction, along with the logo of the subnet in which it was executed

### Internal TXs

<figure><img src="/files/L5bSy0ayuXcrMzXkHRDj" alt=""><figcaption></figcaption></figure>

Internal TXs (Transactions) are operations made inside a transaction that may involve addresses or contracts different that the ones sending or receiving funds. Generally, the more a transactions is complex, the more internal TXs it has.

The results are displayed in different columns:

* **Parent TXN Hash**: The ID of the main transaction
* **Block Info**: the number of the block and the date and hour when the transaction occurred
* **From**: sending address
* **To**: receiving address
* **Value**: the token and its amount, along with the logo of the subnet in which it was executed

### ERC20 TXs

<figure><img src="/files/3HoFSsgvvA9oNNocX8Ca" alt=""><figcaption></figcaption></figure>

This page is similar to the others but here you can only see ERC20 type token transactions.&#x20;

The results are displayed in different columns:

* **Hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed
* **Age:** how much time ago the TX happened included the date and time&#x20;
* **From:** sending address
* **To:** receiving address
* **Value:** token quantity
* **Token:** the name, logo and symbol of the token involved

### ERC721 TXs

<figure><img src="/files/1OWZxInTE9YS5uOxslu4" alt=""><figcaption></figcaption></figure>

As said above, this page involves only ERC721 transactions.

The results are displayed in different columns:

* **Hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed
* **Age:** how much time ago the TX happened included the date and time&#x20;
* **From:** sending address
* **To:** receiving address
* **Token ID:** the identificative number of the Token
* **Token:** symbol, name and logo of the token&#x20;
* **Details:** by clicking here on *view NFT* you'll be redirected to the TX page and be able to see the image

### ERC1155 TXs&#x20;

<figure><img src="/files/tdVwscRcyrSDcB8Yg5OC" alt=""><figcaption></figcaption></figure>

Only ERC1155 type token TX.&#x20;

The results are displayed in different columns:

* **Hash:** or so called Transaction ID, the unique identifier for a transaction, and the subnet in which it was executed
* **Age:** how much time ago the TX happened included the date and time&#x20;
* **From:** sending address
* **To:** receiving address
* **Token ID:** the identificative number of the Token
* **Amount:** the quantity of token involved in the TX process
* **Token:**  symbol, name and logo of the token
* **Details:** by clicking here on *view NFT* you'll be redirected to the TX page and be able to see the image


---

# Agent Instructions: 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.avascan.info/how-to-use-avascan/unified-transaction-list.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.