Tables
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
Columns
Sample Data
Sample Data
Example Query
Example Query
Query with partition filter
events
Blockchain state change notifications emitted by runtime modules during transaction execution and block processing. Contains event metadata (pallet, method, index), encoded parameters, block context, and optional extrinsic linkage for analyzing on-chain activity across Substrate-based chains.Columns
Columns
Sample Data
Sample Data
Example Query
Example Query
Query with partition filter
extrinsics
Substrate blockchain operations submitted to blocks, containing pallet module calls with method parameters, signatures, and execution metadata. Fundamental unit for tracking on-chain state transitions and user interactions across Substrate-based networks.Columns
Columns
Cryptographic signature authorizing the operation. Hex-encoded string format, typically 130-132 characters including 0x prefix for signed transactions and operations. |
|
id | STRING | Unique identifier for the record. String format, specific structure varies by table and blockchain implementation. |
| nonce | INT64 | Sequential counter for transactions or operations from an account. Increments by 1 for each new transaction to prevent replay attacks and ensure transaction ordering. |
| args | JSON | JSON object containing the operation’s input parameters. Structure and fields vary by pallet and method, encoding the specific arguments required to execute the operation. |
| tip | BIGNUMERIC | Optional amount paid to the block producer to prioritize the extrinsic. Numeric value representing additional fee in the chain’s native token denomination, above the standard transaction fee. |
| extrinsic_hash | STRING | Unique identifier for the extrinsic. 66-character hex string including 0x prefix. |
| extrinsic_id | STRING | Composite identifier linking an event or extrinsic to its block and position within that block. Format is \{block_number\}-\{index\} where index represents the sequential position of the extrinsic within the block, starting from 0. |
| info | JSON | JSON object containing metadata about the extrinsic’s execution. Stores information such as weight consumed, fees paid, and dispatch result class for successful operations. |
| immortal_era | NUMERIC | Boolean indicator of whether the transaction has an immortal era. Value of 0 indicates an immortal transaction that never expires; null indicates a mortal transaction with a finite validity period. |
| success | BOOL | Boolean indicator of whether the operation completed successfully without errors. |
| pays_fee | BOOL | Boolean indicator of whether the extrinsic requires a transaction fee to be paid by the submitter. |Sample Data
Sample Data
Example Query
Example Query
Query with partition filter