Skip to main content

Tables

account_changes

NEAR account state changes tracking balance and storage modifications per block. Records both staked and non-staked balance updates with update reasons like receipt processing and gas rewards for analyzing account activity and token flows.
Query with partition filter

block_chunks

Block-level data from NEAR Protocol including validator authors, gas metrics, and total token supply. Used for analyzing block production patterns, network economics, and validator performance across NEAR’s sharded architecture.
Query with partition filter

ft_events

Fungible token (FT) transfer, mint, and burn events following the NEP-141 standard on NEAR Protocol. Tracks balance changes with affected accounts, delta amounts, and transaction context for analyzing token flows and user activity.
Query with partition filter

logs

Event logs emitted by smart contracts during transaction execution, containing indexed topics for efficient filtering and ABI-encoded data payloads. Primary source for tracking contract interactions, token transfers, and state changes across blockchain networks.
Query with partition filter

receipt_actions

Individual actions within NEAR Protocol receipts, including function calls, token transfers, and account operations. Each row represents a single action with execution context (gas price, shard ID, signer) for analyzing smart contract interactions and cross-contract calls.
Query with partition filter

receipts

Cross-shard execution records from NEAR Protocol containing transaction receipts with gas costs, execution status, and account interactions. Used for analyzing smart contract calls, token transfers, and computational resource usage across NEAR’s sharded architecture.
Query with partition filter

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.
Cryptographic signature authorizing the operation. Hex-encoded string format, typically 130-132 characters including 0x prefix for signed transactions and operations. | | status | STRING | Success indicator for the operation. Boolean value where true indicates successful execution and false indicates failure. | | converted_into_receipt_id | STRING | Receipt identifier generated when this transaction is converted into a NEAR receipt for execution. Every NEAR transaction is converted into at least one receipt, represented by this hash value. | | receipt_conversion_gas_burnt | INT64 | Gas consumed (in yoctoGas units) when converting this transaction into a NEAR receipt. Typically ranges from hundreds of billions to trillions for standard actions like function calls and account creation. | | receipt_conversion_tokens_burnt | FLOAT64 | Amount of NEAR tokens burned during transaction-to-receipt conversion, denominated in yoctoNEAR (10^-24 NEAR). Typically ranges from ~30-130 tokens (actual NEAR) based on transaction complexity. | | action_kind | STRING | Type of action executed in this transaction on the NEAR protocol (e.g., FUNCTION_CALL, DELEGATE_ACTION, CREATE_ACCOUNT). Indicates the operation being performed, with DELEGATE_ACTION and FUNCTION_CALL being most common for smart contract interactions. | | args | STRING | 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. | | index_in_transaction | INT64 | Position of this action within the parent transaction, starting from 0. Used to order multiple actions when a single transaction contains several sequential operations. |
Query with partition filter