Litecoin

litecoin holds the standardized Litecoin tables, following the schema documented in the family overview exactly, with no differences.

Tables

Table	Since	Description
`blocks`	2011-10	One row per block, with its fee, size and unspent-output figures already worked out.
`transactions`	2011-10	One row per transaction, with its inputs and outputs nested on the row.

Sample queries

Daily output moved
Chain registry lookup

Measure daily output value moved over one week.

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

Look up Litecoin’s chain entry and the project it belongs to.

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'

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 covers that list of chains and the daily tables built on it. Stacks is the exception in this family: it runs contracts, so its tokens do reach the catalog’s token list.

Overview

Core entities

Core datasets

Market verticals

Chain verticals

Tables

Sample queries

Notes

​Tables

​Sample queries

​Notes

Tables

Sample queries

Notes