injective holds the standardized Injective tables, following the schema documented in the family overview exactly, with no differences.
Injective has two layers, and the catalog treats them as two separate chains. injective is the Cosmos layer, and that is where its tokens and the tokenized assets issued on it are filed. injectiveevm is the EVM layer, where Ethereum-style contracts run; it lives in a dataset of its own, documented under EVM, and that is where the app activity is filed, including the value bridged in from other chains.
The market pages go deeper on each of these. Real-world assets and Stablecoins cover the tokenized assets and their daily tables. Bridges covers transfers between chains, Projects covers app and project activity per chain, and Tokens covers the token list.
Tables
| Table | Since | Description |
|---|---|---|
blocks | 2021-09 | One row per block, with its transaction count and proposer. |
transactions | 2021-09 | One row per transaction, with its fee and result code. |
transaction_messages | 2021-09 | One row per message inside a transaction. |
message_events | 2021-09 | One row per event emitted during transaction execution. |
block_events | 2021-09 | One row per event emitted outside a transaction. |
message_events and block_events are far larger here than on most Cosmos chains. Keep the block_timestamp range narrow and filter on event_type as early in the query as you can.
Sample queries
- Event types by day
- Tokenized assets by market cap
- App activity
Rank event types emitted by transactions on one day.