Noble
Last updated
Last updated
Chain ID: noble_1
For Noble you'll find the following tables (new schema):
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
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 |
---|---|
Field | Type |
---|---|
Field | Type |
---|---|
block_height
STRING
block_timestamp
TIMESTAMP
chain_id
STRING
proposer_address
STRING
validators_hash
STRING
block_height
INTEGER
block_timestamp
TIMESTAMP
event_index
INTEGER
event_type
STRING
event_attributes
JSON
source
STRING
ingestion_timestamp
TIMESTAMP
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
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
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
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