jetton/burns | TON v3

Retrieves a list of Jetton burn events for a specific Jetton address from the TON blockchain

The jetton/burns endpoint retrieves a list of Jetton burn events from the TON blockchain. This endpoint allows you to fetch information about Jettons that have been permanently removed from circulation and provides options for pagination and sorting.

Running the interactive example will return the amount of DOGS burned.

πŸ‘

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

Parameters

  • limit (integer, optional) β€” The maximum number of burn events to return. Default: 128.
  • offset (integer, optional) β€” The number of burn events to skip before starting to return results. Default: 0.
  • sort (string, optional) β€” The sorting order of the burn events. Possible values: asc (ascending) or desc (descending). Default: desc.

Response

  • burns (array) β€” An array of Jetton burn event objects, each containing:
    • jetton (object) β€” Information about the burned Jetton:
      • address (string) β€” The address of the Jetton master contract.
      • name (string) β€” The name of the Jetton.
      • symbol (string) β€” The symbol of the Jetton.
    • burner (object) β€” Information about the account that burned the Jettons:
      • address (string) β€” The address of the burner.
    • transaction (object) β€” Information about the transaction:
      • hash (string) β€” The hash of the transaction.
      • time (integer) β€” The timestamp of the transaction.
    • amount (string) β€” The amount of Jettons burned.
    • comment (string) β€” Any comment attached to the burn event.

Use case

The jetton/burns endpoint is useful for various applications that need to track or analyze Jetton burn activities on the TON blockchain:

  1. Analytics platforms can use this to monitor the reduction in circulating supply of various Jettons.
  2. Wallet applications can show users their history of Jetton burn transactions.
  3. Developers can use this endpoint to build notification systems for significant burn events.
  4. Token issuers can track burn events to manage their token's supply and verify proper functioning of burn mechanisms.
  5. Researchers can analyze burn patterns to study token economics and user behavior.
  6. Compliance tools can use this data to monitor large burns or burns from specific addresses.

Try the jetton/burns RPC method yourself

Language
Click Try It! to start a request and see the response here!