Comment on page
Juno
Chain ID: juno
For Juno you'll find the following tables:
- 1.
juno_blocks
juno_event_attributes
juno_message_event_attributes
juno_transactions
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 |
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 |
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 |
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 |
Last modified 3mo ago