Contains each validated block in the chain. block_timestamp is only available in this table, so you need to do an inner join on block_height to get block_timestamp to the other tables.
Field
Type
Contains all events and their corresponding attributes partitioned by tx_id. Events and their corresponding event_index are relative to the parent transaction , not the message. Events are identified by the event_type column and attributes by the attribute_key. Events are linked to transactions via column tx_id.
Field
Type
Contains all events and their corresponding attributes partitioned by message_index. Events and their corresponding event_index are relative to the parent message_index which is relative to the tx_id. Events are identified by the event_type column and attributes by the attribute_key. Events are linked to transactions via column tx_id.
Field
Type
Contains relevant data associated with a transaction.
Filtered Event-Based Tables
Beyond the raw tables, we have sub-tables for different relevant types of events, such as delegations, redelegations, swaps & voting. You can find them in their respective area (delegations in staking, swaps in liquidity pools, etc.)
Staking Tables
IBC Tables
Liquidity Pools Tables
Governance Tables
Distribution Tables
Additional Data Tables
Additional tables have data that is not event based but relevant when working with event based data.
Purpose: This table decodes token address to denom & stores exponents to parse tokens.
Purpose: This table maps validator addresses to moniker & other metadata.
Each record is a single message triggered within the chain. We include it's type, sender and the corresponding tx_id.
