dydx

Tables

block_events

Block-level events emitted during blockchain processing phases such as BeginBlock, EndBlock, and transaction execution. Contains event type identifiers, sequential indexes, structured attribute data, and block metadata for tracking state changes, validator operations, and protocol-level activities.

Columns

Column	Type	Description
`block_timestamp`	`TIMESTAMP`	Timestamp when the block was produced. UTC timezone, microsecond precision.
`block_height`	`INT64`	Sequential position of the block in the blockchain. Zero-indexed integer representing the block’s distance from the genesis block.
`event_type`	`STRING`	Processing phase within the blockchain’s block lifecycle. Values include ‘initialize’ for events occurring during block initialization, ‘finalize’ for events during block finalization, and chain-specific event type identifiers for transaction-related events.
`event_index`	`INT64`	Sequential position of the event within its containing block. Zero-indexed integer indicating the order in which events occurred during block processing.
`event_attributes`	`JSON`	Structured data containing key-value pairs associated with the blockchain event. JSON object storing event-specific parameters such as amounts, addresses, validators, and transaction identifiers.
`source`	`STRING`	Originating address or processing mode of the blockchain event or message. Format varies by chain: Cosmos-based chains use “BeginBlock” or “EndBlock” for block lifecycle events, TON uses raw or user-friendly address strings, Celestia stores recipient addresses for coin events.

Sample Data

event_index	block_height	block_timestamp	event_attributes
2	1191095	2023-11-15T00:03:39.923Z	{}
3	1191095	2023-11-15T00:03:39.923Z	{}
0	1191095	2023-11-15T00:03:39.923Z	{}

Example Query

Query with partition filter

SELECT *
FROM `tt-blockchain.dydx.block_events`
WHERE block_timestamp >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY)
LIMIT 100

blocks

Block header data containing sequential numbering, cryptographic hashes linking to parent blocks, timestamps, and consensus metadata. Primary source for blockchain state verification and chain navigation.

Columns

Column	Type	Description
`timestamp`	`TIMESTAMP`	Timestamp when the block was produced. UTC timezone.
`block_height`	`INT64`	Sequential position of the block in the blockchain. Zero-indexed integer representing the block’s distance from the genesis block.
`transaction_count`	`INT64`	Number of transactions included in the block.
`validators_hash`	`STRING`	Cryptographic hash of the validator set for the block. Hex-encoded 64-character string without 0x prefix.
`proposer_address`	`STRING`	Address of the validator that proposed the block. Hex-encoded string without 0x prefix, 40 characters in length.

Sample Data

timestamp	block_height	validators_hash	proposer_address	transaction_count
2024-01-08T13:42:23.712Z	5413215	005E689CF8E80A6C78A64637FF4A4C8224053BE1D5329B898DDF6B51FB81C648	06A52B7661D71AC79BF72BAC840170A6D63F57EE	4
2024-01-08T13:42:44.113Z	5413234	005E689CF8E80A6C78A64637FF4A4C8224053BE1D5329B898DDF6B51FB81C648	06A52B7661D71AC79BF72BAC840170A6D63F57EE	5
2024-01-08T13:42:18.631Z	5413210	005E689CF8E80A6C78A64637FF4A4C8224053BE1D5329B898DDF6B51FB81C648	135B0A7F1DB79A8F70A1A1C576500EB3E6F1EFBB	5

Example Query

Query with partition filter

SELECT *
FROM `tt-blockchain.dydx.blocks`
WHERE timestamp >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY)
LIMIT 100

message_events

Events emitted during transaction message processing containing structured attribute data. Tracks state changes, transfers, and smart contract interactions across Cosmos SDK-based blockchains with event type classification and sequential ordering.

Columns

Column	Type	Description
`block_timestamp`	`TIMESTAMP`	Timestamp when the block was produced. UTC timezone, microsecond precision.
`block_height`	`INT64`	Sequential position of the block in the blockchain. Zero-indexed integer representing the block’s distance from the genesis block.
`transaction_hash`	`STRING`	Unique identifier for the transaction. 66-character hex string including 0x prefix.
`event_type`	`STRING`	Processing phase within the blockchain’s block lifecycle. Values include ‘initialize’ for events occurring during block initialization, ‘finalize’ for events during block finalization, and chain-specific event type identifiers for transaction-related events.
`transaction_index`	`INT64`	Position of the transaction within its containing block. Zero-indexed integer indicating the sequential order of transactions in the block.
`message_index`	`STRING`	Sequential position of the message within its containing transaction. Zero-indexed integer indicating the order of messages in multi-message transactions.
`event_index`	`INT64`	Sequential position of the event within its containing block. Zero-indexed integer indicating the order in which events occurred during block processing.
`event_attributes`	`JSON`	Structured data containing key-value pairs associated with the blockchain event. JSON object storing event-specific parameters such as amounts, addresses, validators, and transaction identifiers.

Sample Data

event_type	event_index	block_height	block_timestamp	event_attributes	transaction_hash	transaction_index
tx	44	22562244	2024-08-11T13:14:47.853Z	{“acc_seq”:“dydx1q869gyjwanxhw5xdgfg67pg3y8gjeuzth6u6zl/201474565”,“msg_index”:“0”}	64F7FB51F847BDF58C780558FF9E230347E0D55CDD9232DED2F51D44681D7F58	1
coin_spent	111	22520972	2024-08-11T01:26:26.995Z	{“amount”:“68449ibc/8E27BA2D5493AF5636760E354E46004562C46AB7EC0CC4C1CA14E9E20E2545B5”,“msg_index”:“0”,“spender”:“dydx1v88c3xv9xyv3eetdx0tvcmq7ung3dywp5upwc6”}	2E017CAFB9747098A6EC3D930B8A51DC5080B614B4F6389CAB7D6C43D492716C	1
message	127	22594271	2024-08-11T22:28:51.119Z	{“msg_index”:“0”,“sender”:“dydx1v88c3xv9xyv3eetdx0tvcmq7ung3dywp5upwc6”}	5DF097A11234B78EDAC71B95D3BC82C5B4008B7CB7483B7E47BFB946439E32D5	1

Example Query

Query with partition filter

SELECT *
FROM `tt-blockchain.dydx.message_events`
WHERE block_timestamp >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY)
LIMIT 100

transaction_messages

Individual messages extracted from Cosmos SDK transactions with JSON-encoded payloads and type identifiers. Used for tracking specific blockchain operations like token transfers, staking actions, governance votes, and Inter-Blockchain Communication Protocol (IBC) updates within transaction execution.

Columns

Column	Type	Description
`block_timestamp`	`TIMESTAMP`	Timestamp when the block was produced. UTC timezone, microsecond precision.
`block_height`	`INT64`	Sequential position of the block in the blockchain. Zero-indexed integer representing the block’s distance from the genesis block.
`transaction_hash`	`STRING`	Unique identifier for the transaction. 66-character hex string including 0x prefix.
`transaction_index`	`INT64`	Position of the transaction within its containing block. Zero-indexed integer indicating the sequential order of transactions in the block.
`message_index`	`INT64`	Sequential position of the message within its containing transaction. Zero-indexed integer indicating the order of messages in multi-message transactions.
`message_type`	`STRING`	Protocol-specific identifier for the transaction message operation. Forward-slash delimited string indicating the message’s module and action, such as IBC (Inter-Blockchain Communication) client updates, governance votes, or protocol-specific operations.
`message`	`STRING`	JSON-encoded payload containing the transaction message data and parameters. Structure and fields vary by message type, with nested objects representing protocol-specific operations and state changes.

Sample Data

message	block_height	message_type	block_timestamp	transaction_hash
{“operationsQueue”:[],“@type”:“/dydxprotocol.clob.MsgProposedOperations”}	11858971	/dydxprotocol.clob.MsgProposedOperations	2024-03-27T21:45:28.191Z	C539625BF1F515BA15241F61651287B1A8F052014392B34C1A72C7449539C122
{“operationsQueue”:[],“@type”:“/dydxprotocol.clob.MsgProposedOperations”}	11836267	/dydxprotocol.clob.MsgProposedOperations	2024-03-27T15:08:43.823Z	C539625BF1F515BA15241F61651287B1A8F052014392B34C1A72C7449539C122
{“operationsQueue”:[],“@type”:“/dydxprotocol.clob.MsgProposedOperations”}	11807722	/dydxprotocol.clob.MsgProposedOperations	2024-03-27T06:48:31.969Z	C539625BF1F515BA15241F61651287B1A8F052014392B34C1A72C7449539C122

Example Query

Query with partition filter

SELECT *
FROM `tt-blockchain.dydx.transaction_messages`
WHERE block_timestamp >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY)
LIMIT 100

transactions

Transaction records containing signed operations that modify blockchain state. Primary source for tracking value transfers, contract interactions, and account state changes across the network.

Columns

Column	Type	Description
`block_height`	`INT64`	Sequential position of the block in the blockchain. Zero-indexed integer representing the block’s distance from the genesis block.
`block_timestamp`	`TIMESTAMP`	Timestamp when the block was produced. UTC timezone, microsecond precision.
`transaction_hash`	`STRING`	Unique identifier for the transaction. 66-character hex string including 0x prefix.
`transaction_index`	`INT64`	Position of the transaction within its containing block. Zero-indexed integer indicating the sequential order of transactions in the block.
`transaction_info`	`STRING`	Additional metadata or context information for the transaction. Empty string when no additional information is available.
`transaction_log`	`STRING`	Execution event log data from the transaction. JSON-encoded array containing message indexes, event types, and key-value attribute pairs documenting state changes and actions performed during transaction execution.
`transaction_code`	`INT64`	Status code indicating the transaction execution result. 0 represents successful execution, non-zero values indicate various error conditions.
`transaction_fee`	`BIGNUMERIC`	Transaction fee paid for processing the transaction. Denominated in the network’s native token with smallest unit precision.
`transaction_tip`	`BIGNUMERIC`	Optional gratuity paid to validators for transaction prioritization. Denominated in the network’s native token with smallest unit precision.
`gas_wanted`	`STRING`	Maximum gas units allocated for the transaction execution. String-encoded integer representing the computational resource limit set by the transaction submitter.
`gas_used`	`STRING`	Amount of gas consumed by the execution. Measured in gas units, representing the computational resources used to process the operation.

Sample Data

block_height	block_timestamp	transaction_log	transaction_code	transaction_hash
28255623	2024-10-21T00:11:47.467Z	tx parse error	2	20281F98DFDCF3C6FE8C0B5EB2AA629D1331A3FAEADF1DEDC017C9D364C6D845
28274269	2024-10-21T05:58:49.803Z	tx parse error	2	2174C6B608BDDC8E3696A5DF84903DDE7B09FC1DD68A4F204F7515258E1E7E4E
28277883	2024-10-21T07:04:25.102Z	tx parse error	2	0FF42C80B58145B090D5FEB89BB143781E6F72FB7718E3122447040C76048372

Example Query

Query with partition filter

SELECT *
FROM `tt-blockchain.dydx.transactions`
WHERE block_timestamp >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY)
LIMIT 100

Overview

Metrics

Primitives

Contracts

Blockchain

Tables

block_events

blocks

message_events

transaction_messages

transactions

​Tables

​block_events

​blocks

​message_events

​transaction_messages

​transactions

Tables

block_events

blocks

message_events

transaction_messages

transactions