> ## Documentation Index
> Fetch the complete documentation index at: https://tokenterminal.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To query the Token Terminal data catalog, read https://tokenterminal.com/docs/catalog/agents-manual.md first. It is the whole catalog as one page: table naming grammar, key columns, partition and cluster rules, units, additivity, and the tables that are documented but not served yet.
> Never query a catalog table on a time bound alone. Also filter its cluster key, which you read from INFORMATION_SCHEMA.COLUMNS; an empty result means the object is a view, whose pruning contract is on its page. Compute is billed to the caller's own Google Cloud project.

# Tron

> Standardized Tron tables from June 2018.

`tron` holds the standardized Tron tables. They look much like the tables for the EVM chains, the ones running the Ethereum Virtual Machine: `blocks`, `transactions` and `logs`, plus two more for the transfers Tron handles in its own way rather than through contracts: `internal_transactions` and `wallet_blocks`.

Tron writes an address in two forms, and both are here. The columns named `*_hex` hold the form that looks like an Ethereum address; the plain `address`-style columns hold the base58 form, the one that starts with a T and appears in wallets and explorers. Pick whichever matches the addresses you are joining against.

Above the raw tables sits the rest of the catalog, and Tron shows up in two parts of it: the tokenized assets issued on it, and the list of tokens we know about with their daily prices. Stablecoins dominate the asset side.

The market pages go deeper on each of these. [Stablecoins](https://tokenterminal.com/docs/catalog/stablecoins/index.md) and [Real-world assets](https://tokenterminal.com/docs/catalog/real-world-assets/index.md) cover the tokenized assets and their daily tables. [Tokens](https://tokenterminal.com/docs/catalog/tokens/index.md) covers the token list and the daily price table.

## Tables

<table>
  <thead>
    <tr>
      <th width="200">Table</th>
      <th width="90">Since</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>`blocks`</td>
      <td>2018-06</td>
      <td>One row per block, following the EVM block shape.</td>
    </tr>

    <tr>
      <td>`transactions`</td>
      <td>2018-06</td>
      <td>One row per transaction, with what it cost and the resources it used on the same row.</td>
    </tr>

    <tr>
      <td>`logs`</td>
      <td>2018-10</td>
      <td>One row per contract event log, following the EVM log shape.</td>
    </tr>

    <tr>
      <td>`internal_transactions`</td>
      <td>2018-10</td>
      <td>One row per internal transaction, with per-token values in `call_value_info`.</td>
    </tr>

    <tr>
      <td>`wallet_blocks`</td>
      <td>2018-06</td>
      <td>One row per native wallet action, linked to its transaction.</td>
    </tr>
  </tbody>
</table>

Blocks are keyed on `number`, transactions on `transaction_hash`, and logs on `block_number` with `log_index`.

Tron meters two resources in place of a single gas fee: energy for running contracts and bandwidth for the size of a transaction, and an account can hold an allowance of either. The `receipt_info_energy_fee`, `receipt_info_energy_usage_total` and `receipt_info_net_fee` columns on `transactions` record that, a set of columns particular to Tron.

## Sample queries

**Daily transactions and fees**

**Sum daily transactions and energy fees over one week.**

```sql theme={null}
select
    timestamp_trunc(block_timestamp, day) as day,
    count(*) as transactions,
    sum(receipt_info_energy_fee) as energy_fee_sun
from `tron.transactions`
where block_timestamp >= timestamp('2026-08-16')
  and block_timestamp < timestamp('2026-08-23')
group by day
order by day
```

**Tokenized assets ranked**

**Rank the tokenized assets issued on Tron by circulating market cap.**

```sql theme={null}
select
    assets.symbol,
    assets.asset_type,
    daily.market_cap_circulating
from `metrics_asset_tokens.market_cap_circulating_daily` as daily
join `dimensions.asset_tokens` as deployments
    using (asset_token_id)
join `dimensions.assets` as assets
    using (asset_id)
where daily.timestamp >= timestamp('2026-08-22')
  and daily.timestamp < timestamp('2026-08-23')
  and deployments.chain_id = 'tron'
order by daily.market_cap_circulating desc
```

**Priced tokens, daily**

**Count the Tron tokens that have a daily USD price, day by day.**

```sql theme={null}
select
    date(timestamp) as day,
    count(distinct token_id) as priced_tokens
from `metrics_tokens.price_daily`
where timestamp >= timestamp('2026-08-16')
  and timestamp < timestamp('2026-08-23')
  and chain_id = 'tron'
group by day
order by day
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.