Terra 2

Chain ID: phoenix_1

For Sei you'll find the following tables:

1. Raw Tables

2. Additional Data Tables

Raw Tables

phoenix_blocks

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
block_height	STRING
block_timestamp	TIMESTAMP
chain_id	STRING
proposer_address	STRING
validators_hash	STRING

phoenix_event_attributes

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
block_height	INTEGER
chain_id	STRING
tx_id	STRING
event_index	INTEGER
event_type	STRING
attribute_key	STRING
attribute_value	STRING
attribute_index	INTEGER
ingestion_timestamp	TIMESTAMP

phoenix_message_event_attributes

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
block_height	STRING
chain_id	STRING
tx_id	STRING
message_index	INTEGER
event_index	INTEGER
event_type	STRING
attribute_key	STRING
attribute_value	STRING
attribute_index	INTEGER
ingestion_timestamp	TIMESTAMP

phoenix_transactions

Contains relevant data associated with a transaction.

Field	Type
block_height	STRING
chain_id	STRING
tx_id	STRING
tx_status	STRING
fee	STRING
tx_code	INTEGER
tx_index	INTEGER
gas_used	INTEGER
gas_wanted	INTEGER
ingestion_timestamp	TIMESTAMP

phoenix_tx_messages

Contains all messages submitted to the blockchain. Each row is one message, so there might be repeated tx_id if the transaction has more than one message.

Field	Type
block_height	STRING
chain_id	STRING
tx_id	STRING
tx_index	INTEGER
message_index	INTEGER
message_type	STRING
message	JSON
schema_version	INTEGER
block_timestamp	TIMESTAMP
ingestion_timestamp	TIMESTAMP

Additional Data Tables:

Additional tables have data that is not event-based but relevant when working with event-based data.

validators

Purpose: This table maps validator addresses to moniker & other metadata.

Field	Type
account_address	STRING
operator_address	STRING
consensus_pubkey	STRING
status	FLOAT
moniker	STRING
identity	STRING
rate	STRING
max_rate	FLOAT
min_self_delegation	FLOAT
Network	STRING
Snapshot_date	TIMESTAMP