> ## 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.

# Litecoin

> Standardized Litecoin tables from October 2011.

`litecoin` holds the standardized Litecoin tables, following the schema documented in [the family overview](/docs/catalog/chain-verticals/bitcoin/index) exactly, with no differences.

## Tables

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

  <tbody>
    <tr>
      <td><code>blocks</code></td>
      <td>2011-10</td>
      <td>One row per block, with its fee, size and unspent-output figures already worked out.</td>
    </tr>

    <tr>
      <td><code>transactions</code></td>
      <td>2011-10</td>
      <td>One row per transaction, with its inputs and outputs nested on the row.</td>
    </tr>
  </tbody>
</table>

## Sample queries

<Tabs>
  <Tab title="Daily output moved">
    **Measure daily output value moved over one week.**

    ```sql theme={null}
    select
        timestamp_trunc(block_timestamp, day) as day,
        count(*) as transactions,
        sum((select sum(output.value) from unnest(outputs) as output)) as total_output_value
    from `litecoin.transactions`
    where block_timestamp >= timestamp('2026-08-16')
      and block_timestamp < timestamp('2026-08-23')
    group by day
    order by day
    ```
  </Tab>

  <Tab title="Chain registry lookup">
    **Look up Litecoin's chain entry and the project it belongs to.**

    ```sql theme={null}
    select
        chains.chain_id,
        chains.name as chain_name,
        projects.name as project_name,
        projects.primary_market_sector
    from `dimensions.chains` as chains
    join `dimensions.projects` as projects using (project_id)
    where chains.chain_id = 'litecoin'
    ```
  </Tab>
</Tabs>

## Notes

Both tables cover the chain's full history and run to the current day.

Litecoin has no tokens, no apps and no trading pools, so the catalog tables built on those things hold nothing for it. The list of chains we track is the one catalog table that carries Litecoin, and everything else for the chain comes from `litecoin` above.

[Chains](/docs/catalog/chains/index) covers that list of chains and the daily tables built on it. [Stacks](/docs/catalog/chain-verticals/bitcoin/stacks) is the exception in this family: it runs contracts, so its tokens do reach the catalog's token list.