Substrate ecosystem

Substrate is the framework Polkadot and the chains connected to it are built with. These chains call a transaction an extrinsic, and running one produces events: the chain’s notes on what happened. That gives every chain here the same three tables, blocks, extrinsics and events, in one dataset per chain. The Tables section below says what each table holds and lists the columns once for the whole family.

Chains

Chain	`chain_id`	blocks	events	extrinsics
Astar	`astar`	✓	✓	✓
Chainflip	`chainflip`	✓	✓	✓
Energy Web	`energyweb`	✓	✓	✓
Hydration	`hydradx`	✓	✓	✓
Kusama	`kusama`	✓	✓	✓
Litentry	`litentry`	✓	✓	✓
peaq	`peaq`	✓	✓	✓
Polkadot	`polkadot`	✓	✓	✓
Polkadot Asset Hub	`polkadotassethub`	✓	✓	✓
Polkadot Bridge Hub	`polkadotbridgehub`	✓	✓	✓
Polkadot Collectives	`polkadotcollectives`	✓	✓	✓
Polkadot Coretime	`polkadotcoretime`	✓	✓	✓
Polkadot People	`polkadotpeople`	✓	✓	✓

Tables

Substrate is the framework Polkadot and its parachains are built with, and every chain built that way carries the same three core tables with the same columns. The schemas below are read from polkadot, and apply to every chain listed on the Substrate overview. Three words to know before the tables. An extrinsic is what these chains call a transaction: something submitted from outside the chain for it to act on. A pallet is one module of the chain’s own code, such as balances, staking or governance, and an extrinsic names the pallet and the method it wants. An event is a note the chain writes about what happened while running one. extrinsics and events are split by day on block_timestamp, and blocks on timestamp. Filter on that column in every query: with a filter the query reads only the days you asked for, without one it reads the whole table.

blocks
extrinsics
events

A block is a batch of extrinsics added to the chain. blocks contains one row per block.

Column	Type	Description
`relay_chain`	`STRING`	The main chain this one connects to, Polkadot or Kusama.
`chain`	`STRING`	The chain name.
`timestamp`	`TIMESTAMP`	The time the block was produced. Partition column.
`number`	`INT64`	The block number.
`block_hash`	`STRING`	The hash of the block.
`parent_hash`	`STRING`	The hash of the parent block.
`state_root`	`STRING`	The root hash of the state trie.
`extrinsics_root`	`STRING`	The root hash of the extrinsics trie.
`author_id`	`STRING`	The account that authored the block.
`finalized`	`BOOL`	Whether the block is finalized.
`block_date`	`TIMESTAMP`	The block timestamp truncated to the day.
`extrinsics_count`	`INT64`	The number of extrinsics in the block.

Daily blocks and extrinsics

Count blocks and total extrinsics per day over one week.

select
    timestamp_trunc(timestamp, day) as day,
    count(*) as blocks,
    sum(extrinsics_count) as extrinsics
from `polkadot.blocks`
where timestamp >= timestamp('2026-08-16')
  and timestamp < timestamp('2026-08-23')
group by day
order by day

extrinsics contains one row per extrinsic. Group by pallet and method to see what the chain was asked to do; some extrinsics carry no signature and no fee, because the chain itself submitted them.

Column	Type	Description
`relay_chain`	`STRING`	The main chain this one connects to, Polkadot or Kusama.
`chain`	`STRING`	The chain name.
`block_number`	`INT64`	The number of the containing block.
`block_timestamp`	`TIMESTAMP`	The time of the containing block. Partition column.
`block_hash`	`STRING`	The hash of the containing block.
`pallet`	`STRING`	The part of the chain’s code the call goes to, such as balances or staking.
`method`	`STRING`	The method called in that pallet.
`signature`	`STRING`	Who signed the extrinsic and their proof. Empty when the chain submitted it itself.
`id`	`STRING`	The identifier of the extrinsic.
`nonce`	`INT64`	The sender’s nonce.
`args`	`JSON`	The call arguments.
`tip`	`BIGNUMERIC`	The tip paid to the block author.
`extrinsic_hash`	`STRING`	The hash of the extrinsic.
`extrinsic_id`	`STRING`	The block-number-and-index identifier of the extrinsic.
`info`	`JSON`	What running it cost, including its weight and fee class.
`immortal_era`	`NUMERIC`	The mortality setting of the extrinsic.
`success`	`BOOL`	Whether the extrinsic succeeded.
`pays_fee`	`BOOL`	Whether the extrinsic pays a fee.

Pallet calls

Rank pallet calls by executed extrinsics over one week.

select
    pallet,
    method,
    count(*) as extrinsics
from `polkadot.extrinsics`
where block_timestamp >= timestamp('2026-08-16')
  and block_timestamp < timestamp('2026-08-23')
group by pallet, method
order by extrinsics desc
limit 20

events contains one row per event, each linked back to the extrinsic that produced it. Watch the column names here: pallet and method describe that extrinsic, while event_pallet and event_method describe the event itself.

Column	Type	Description
`relay_chain`	`STRING`	The main chain this one connects to, Polkadot or Kusama.
`chain`	`STRING`	The chain name.
`block_number`	`INT64`	The number of the containing block.
`block_timestamp`	`TIMESTAMP`	The time of the containing block. Partition column.
`block_hash`	`STRING`	The hash of the containing block.
`pallet`	`STRING`	The pallet of the extrinsic that produced the event, not of the event itself.
`method`	`STRING`	The method of that extrinsic.
`id`	`STRING`	The identifier of the event.
`extrinsic_hash`	`STRING`	The hash of the producing extrinsic.
`extrinsic_id`	`STRING`	The identifier of the producing extrinsic.
`success`	`BOOL`	Whether the producing extrinsic succeeded.
`event_method`	`STRING`	The method of the event itself.
`event_pallet`	`STRING`	The pallet that emitted the event.
`event_data`	`ARRAY<JSON>`	The event payload fields.
`event_index`	`INT64`	The position of the event within the block.
`event_type`	`STRING`	The type label of the event.

Event-emitting pallets

Rank event-emitting pallets and methods over one week.

select
    event_pallet,
    event_method,
    count(*) as events
from `polkadot.events`
where block_timestamp >= timestamp('2026-08-16')
  and block_timestamp < timestamp('2026-08-23')
group by event_pallet, event_method
order by events desc
limit 20

Exceptions

One chain carries more than the three core tables. Polkadot adds chain_ids, a small lookup table, and initialize_finalize_events, which holds the events the chain writes at the start and end of a block rather than while running an extrinsic. Every other chain has exactly the three core tables.

Overview

Core entities

Core datasets

Market verticals

Chain verticals

Chains

Tables

Exceptions

​Chains

​Tables

​Exceptions

Chains

Tables

Exceptions