# Token Transfer

This screen displays a token transfer history dashboard for a BlockDAG-based blockchain network. It shows recent token transactions, including minting and transfers, along with details such as transaction hash, method, block number, age, sender, receiver, amount, and transaction fee.

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

#### **Total Transactions**&#x20;

At the top, it states that there are ***"63,711"*** total token transactions recorded. However, only a few transactions are shown on each page. Since there are ***"6,372"*****&#x20;pages**, users can browse through transactions using pagination controls at the bottom.&#x20;

#### **Transaction Hash (TXN HASH)**

Each transaction has a unique identifier called a transaction hash *(TXN HASH)*. This acts as a digital receipt for the transaction. It is displayed in a shortened format *(for example, **0xe01...87850**)* to make it easier to read. If users click on the transaction hash (if supported), they can view detailed transaction data, including gas fees, confirmations, and timestamps.

#### **Transaction Method**

The method column indicates the type of transaction. There are two main methods visible in the image:

1. **Mint:** This means new tokens were created and added to circulation. Minting transactions are usually done by a contract or a central authority.
2. **Transfer:** This means tokens were sent from one wallet to another. Transfers occur when users or smart contracts move tokens.

#### **Block Number**

Each transaction belongs to a specific block in the blockchain. The block number represents when the transaction was confirmed. For example, one transaction is in ***"Block 7283"***, while another is in ***"Block 7277"***. Higher block numbers mean more recent transactions. This helps users determine how long ago a transaction was processed.

#### **Transaction Age**

The age column shows how much time has passed since the transaction was added to the blockchain. For example, some transactions in the image occurred ***"2 days ago"***, while others happened ***"3 days ago"***. This information helps users track how recent or old a transaction is.

#### **Sender and Receiver&#x20;*****(From and To)***

The **From** column shows the wallet address that initiated the transaction, while the To column shows the recipient wallet address. Wallet addresses are displayed in a shortened format *(for example, **0x321...35Cde**)* to keep the display clean. If the same wallet appears in both From and To columns, it could indicate that the user is minting tokens for themselves or performing a contract-related operation.

#### **Transaction Amount**

The amount column shows how many tokens were transferred or minted in the transaction. In the image, some transactions transferred **$10**, while others moved **$5**. One transaction shows **$10T**, which could mean 10 trillion tokens or another token unit. The last transaction in the list shows **$0**, which might indicate a failed transaction or a token approval request.

#### **Transaction Fee (TXN FEE)**

The **transaction fee column displays the cost of processing the transaction**. In this image, all transactions have a fee of **$0**, which could mean:

1. The blockchain does not charge transaction fees, or it is a test network.
2. The sender has special permissions that allow free transactions.
3. The transactions were covered by a third party, such as a contract owner.


---

# 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.blockdagnetwork.io/block-explorer/evm/tokens-list/token-transfer.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.