Injective

injective holds the standardized Injective tables, following the schema documented in the family overview exactly, with no differences. Injective also runs a second layer where Ethereum-style contracts work, and that lives in a separate dataset, injectiveevm, documented under EVM.

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.

Sample queries

Event types by day
Tokenized assets by market cap
App activity

Rank event types emitted by transactions on one day.

select
    event_type,
    count(*) as events
from `injective.message_events`
where block_timestamp >= timestamp('2026-08-20')
  and block_timestamp < timestamp('2026-08-21')
group by event_type
order by events desc
limit 20

Rank the tokenized assets deployed on the Cosmos layer by circulating market cap.

select
    assets.symbol,
    assets.asset_type,
    daily.market_cap_circulating_total
from `metrics_asset_tokens.market_cap_circulating_total_daily` as daily
join `dimensions.asset_tokens` as deployments
    using (asset_token_id)
join `dimensions.assets` as assets
    using (asset_id)
where daily.timestamp >= timestamp('2026-08-22')
  and daily.timestamp < timestamp('2026-08-23')
  and deployments.chain_id = 'injective'
order by daily.market_cap_circulating_total desc

Rank the apps active on the EVM layer by fees over one week.

select
    apps.name,
    sum(daily.fees) as fees
from `metrics_app_chains.fees_daily` as daily
join `dimensions.apps` as apps
    using (app_id)
where daily.timestamp >= timestamp('2026-08-16')
  and daily.timestamp < timestamp('2026-08-23')
  and daily.chain_id = 'injectiveevm'
group by apps.name
order by fees desc

Notes

Injective runs its whole exchange on the chain itself, and every order and trade leaves a note behind, so 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. 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, 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. Tokenized 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.

Overview

Core entities

Core datasets

Market verticals

Chain verticals

Tables

Sample queries

Notes

​Tables

​Sample queries

​Notes

Tables

Sample queries

Notes