# Token transactions

This page lists **fungible token** activity (e.g., [TIP-3](https://docs.everscale.network/standard/TIP-3)) that changed an account’s token balance.

Each row shows:

* **Transaction** — ID and type (click to open the [transaction details](https://docs.everscan.io/transactions#transaction-details))
* **From /** **To** — sender and recipient addresses (click for [account details](https://docs.everscan.io/accounts#account-details))
* **Token** — token name/symbol (click for [token details](https://docs.everscan.io/tokens#token-details))
* **Balance** **change** — amount of tokens debited (−) or credited (+) to the account
* **Time** — timestamp

You can filter by **date range**, **transaction type,** and **token/whitelist** using the controls at the top. Use **Export to .csv** to download the table.

![](https://290096163-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6kFtbSuFKuhysj5cGjsO%2Fuploads%2FJdyiSELS2QlNtwzrP9U3%2Fimage.png?alt=media\&token=39152202-72d9-4356-86c5-c9d8e36eba79)

### Transaction types

Transactions are grouped into the following types:

* **Mint —** New tokens are created and credited to an account, increasing total supply.
* **Burn** — Tokens are destroyed, reducing total supply.
* **Transfer** — Tokens are sent from **From** to **To**.
* **Receive** — The **incoming** side of a transfer (tokens credited to the recipient).
* **Revert** **send** — A transfer **failed/bounced** and tokens were returned to the sender (e.g., recipient wallet not deployed or invalid destination for `transferToWallet`).
* **Revert burn** is used to return tokens if the owner of the tokens cancels the `burn`.


---

# 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.everscan.io/use/token-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.