Noble

Chain ID: noble_1

For Noble you'll find the following tables (new schema):

1. Raw Tables

Raw Tables

When querying in BigQeury make sure you add the prefix noble_ to all of the name tables below. For example, the table blocks should be:

select * from numia-data.noble.noble_blocks

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

block_events

Contains all events and their corresponding attributes partitioned by block_height. Does not contain events triggered from messages and transactions signed by addresses. Events and their corresponding event_index are relative to the parent block , not the message or transactions. Events are identified by the event_type column and contains attributes by identified by attribute_key.

Field	Type
block_height	INTEGER
block_timestamp	TIMESTAMP
event_index	INTEGER
event_type	STRING
event_attributes	JSON
source	STRING
ingestion_timestamp	TIMESTAMP

message_event

Contains all events and their corresponding attributes partitioned by tx_id and 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 can be extracted in event_atributes. Events are linked to transactions via column tx_id.

Field	Type
block_height	STRING
block_timestamp	TIMESTAMP
tx_hash	STRING
tx_index	INTEGER
message_index	INTEGER
event_index	INTEGER
event_type	STRING
event_attributes	JSON
ingestion_timestamp	TIMESTAMP

transactions

Contains relevant data associated with a transaction.

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

tx_messages

Contains the messages and their corresponding payload. Partitioned by tx_id where the combination of tx_id and message_index makes up the primary key.

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

validators

Contains all information about active and non-active validators.

operator_address	STRING
account_address	STRING
consensus_pubkey	STRING
jailed	BOOLEAN
status	STRING
tokens	STRING
moniker	STRING
identity	STRING
website	STRING
security_contact	STRING
details	STRING
unbonding_height	INTEGER
unbonding_time	DATETIME
commission_rate	FLOAT
commission_max_rate	FLOAT
commission_max_change_rate	FLOAT
commission_update_time	DATETIME
min_self_delegation	BIGNUMERIC
snapshot_height	INTEGER
snapshot_time	DATETIME
ingestion_timestamp	TIMESTAMP