Dataset schemas

This page describes Blockchain Analytics table schemas.

Arbitrum One

Tables available for analysis

  • blocks: Table holding Arbitrum block data.
  • decoded_events: Table holding decoded event data for a variety of popular Arbitrum event types.
  • logs: Table holding Arbitrum event logs emitted during on-chain activity.
  • receipts: Table holding transaction receipts, data about outcomes of transactions.
  • transactions: Table holding transactions which are actions initiated by externally owned accounts.

Avalanche Contract Chain

Tables available for analysis

  • blocks: Table holding Avalanche block data.
  • decoded_events: Table holding decoded event data for a variety of popular Avalanche event types.
  • logs: Table holding Avalanche event logs emitted during on-chain activity.
  • receipts: Table holding transaction receipts, data about outcomes of transactions.
  • transactions: Table holding transactions which are actions initiated by externally owned accounts.

Cronos Mainnet

Tables available for analysis

  • blocks: Table holding Cronos block data.
  • decoded_events: Table holding decoded event data for a variety of popular Cronos event types.
  • logs: Table holding Cronos event logs emitted during on-chain activity.
  • receipts: Table holding transaction receipts, data about outcomes of transactions.
  • transactions: Table holding transactions which are actions initiated by externally owned accounts.

Ethereum Goerli

Tables available for analysis

  • blocks: Table holding Ethereum Goerli block data.
  • decoded_events: Table holding decoded event data for a variety of popular Ethereum Goerli event types.
  • logs: Table holding Ethereum Goerli event logs emitted during on-chain activity.
  • receipts: Table holding transaction receipts, data about outcomes of transactions.
  • transactions: Table holding transactions which are actions initiated by externally owned accounts.

Ethereum Mainnet

Tables available for analysis

  • accounts_state: Table holding account state at block heights where the account was seen transacting on-chain (excludes internal transactions).
  • blocks: Table holding Ethereum block data.
  • decoded_events: Table holding decoded event data for a variety of popular Ethereum event types.
  • logs: Table holding Ethereum event logs emitted during on-chain activity.
  • receipts: Table holding transaction receipts, data about outcomes of transactions.
  • token_transfers: Table holding ERC-20, ERC-721, and ERC-1155 token transfers.
  • traces: Table holding Parity-style traces which show actions executed by the EVM for some specific transaction or block reward.
  • transactions: Table holding transactions which are actions initiated by externally owned accounts.

Clustered materialized views

  • accounts: Identifies accounts as externally owned accounts or smart contracts with the following schema, clustered on address.

    Field name BigQuery type Description
    address STRING Address identifying the account.
    code STRING Compiled runtime bytecode of this account, given the account is a smart contract.
    code_hash STRING Hash of the code of the account. For all externally-owned accounts this will be 0xc5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470. This is the hash when there is no code present.
    is_contract BOOLEAN Whether or not this address is a smart contract. True, if the address identifies a smart contract.
  • accounts_state_by_address: Materialized view that has the same schema as the accounts_state table and clusters the data on the address column.

  • transactions_by_from_address: Materialized view that has the same schema as the transactions table and clusters the data on the from_address column.

  • transactions_by_to_address: Materialized view that has the same schema as the transactions table and clusters the data on the to_address column.

Fantom Opera

Tables available for analysis

  • blocks: Table holding Fantom block data.
  • decoded_events: Table holding decoded event data for a variety of popular Fantom event types.
  • logs: Table holding Fantom event logs emitted during on-chain activity.
  • receipts: Table holding transaction receipts, data about outcomes of transactions.
  • transactions: Table holding transactions which are actions initiated by externally owned accounts.

Optimism Mainnet

Tables available for analysis

  • blocks: Table holding Optimism block data.
  • decoded_events: Table holding decoded event data for a variety of popular Optimism event types.
  • logs: Table holding Optimism event logs emitted during on-chain activity.
  • receipts: Table holding transaction receipts, data about outcomes of transactions.
  • transactions: Table holding transactions which are actions initiated by externally owned accounts.

Polygon Mainnet

Tables available for analysis

  • blocks: Table holding Polygon block data.
  • decoded_events: Table holding decoded event data for a variety of popular Polygon event types.
  • logs: Table holding Polygon event logs emitted during on-chain activity.
  • receipts: Table holding transaction receipts, data about outcomes of transactions.
  • transactions: Table holding transactions which are actions initiated by externally owned accounts.

Tron Mainnet

Tables available for analysis

  • blocks: Table holding Tron block data.
  • decoded_events: Table holding decoded event data for a variety of popular Tron event types.
  • logs: Table holding Tron event logs emitted during on-chain activity.
  • receipts: Table holding transaction receipts, data about outcomes of transactions.
  • transactions: Table holding transactions which are actions initiated by externally owned accounts.

BigQuery schemas

Please reference the Schema tab of each table in BigQuery:

Schema tab, BigQuery

Column description,
BigQuery