# Data

Here's a brief message example:

<figure><img src="/files/880PHuSSo9bBWqhVEl3v" alt="Screenshot sample from the Burns Tool" width="359"><figcaption></figcaption></figure>

In this case, this was a liquidity burn for the token FLOKI (example), paired with WETH.

## Header

* **What happened**\
  Clickable event, will lead you to the Etherscan transaction's page.
* **Type of burn**\
  Can be Liquidity, Token or NFT.
* **Liquidity pair that was burned** — **Uniswap pair dex**\
  Clickable, will lead you each of the tokens' Etherscan page.
* **Address of burner**\
  Clickable, will lead you to the address' Etherscan page

## Middle Section

Amount of Liquidity or Token burned compared to the total supply.\
**If 100%, a nuke emoji ☢️ will be displayed.**

If the event is a Token Burn, the message will also display the amount of tokens remaining in the burner's wallet.

## Bottom:

* **Contract Address**
* Token **Market Cap**
* **Links for charts**:\
  DexScreener, DexView, DexTools, DexSpy
* **Links to buy/sell the token** (referral)\
  Maestro, Maestro Pro, BananaGun, Photon

Why is a burn important? Read: [Burns](/home/tools/eth-suite/burns.md)


---

# 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://cerbero-tools.gitbook.io/home/tools/eth-suite/burns/data.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.