Skip to main content
Schema: near.core Table: fact_transactions Type: View

​
What

​
Description

This table contains all transactions processed on the NEAR Protocol blockchain, providing comprehensive transaction metadata including signer and receiver information, gas consumption, fees, and execution status. The data captures the complete transaction lifecycle from submission to finalization, including cryptographic signatures, nonce values, and gas mechanics. This table serves as the primary fact table for transaction-level analytics and provides the foundation for understanding user activity, contract interactions, and network utilization patterns.

​
Key Use Cases

  • Transaction volume analysis and network activity monitoring
  • User behavior analysis and wallet activity tracking
  • Gas consumption analysis and fee optimization studies
  • Contract interaction analysis and smart contract usage patterns
  • Transaction success rate analysis and failure investigation
  • Cross-account transaction flow analysis and network mapping
  • Economic analysis of transaction fees and gas pricing

​
Important Relationships

  • Links to core.fact_blocks through block_id for temporal and block context
  • Connects to core.fact_receipts through tx_hash for execution outcome details
  • Provides transaction context for core.fact_logs and core.fact_token_transfers
  • Supports core.ez_actions for detailed action-level analysis
  • Enables analysis in defi.ez_dex_swaps and defi.ez_bridge_activity through transaction context
  • Powers stats.ez_core_metrics_hourly for aggregated transaction metrics

​
Commonly-used Fields

  • tx_hash: Essential for unique transaction identification and blockchain verification
  • block_timestamp: Primary field for time-series analysis and trend detection
  • tx_signer and tx_receiver: Critical for user activity analysis and network mapping
  • gas_used and transaction_fee: Important for economic analysis and cost optimization
  • tx_succeeded: Essential for success rate analysis and failure investigation
  • attached_gas: Important for understanding gas mechanics and transaction planning
  • nonce: Critical for transaction ordering and replay protection analysis

​
Columns

Column NameData TypeDescription
TX_HASHTEXTUnique identifier (hash) of this transaction.
BLOCK_IDNUMBERThe height of the chain this block corresponds with.
BLOCK_TIMESTAMPTIMESTAMP_NTZThe date and time at which the block began.
NONCENUMBERNonce for transactions.
SIGNATURETEXTThe signature taken from block headers.
TX_RECEIVERTEXTThe transaction receiver, similar to an origin_to in EVM, but can be a contract OR if a relayer is used, the receiver is the user. This field identifies the account that is the intended recipient of the transaction. In direct transactions, this is typically the contract or account being called. In relay transactions, this represents the end user account that the relayer is acting on behalf of.
TX_SIGNERTEXTAccount that originally signed the transaction, can be a relayer. This field identifies the account that cryptographically signed the transaction, authorizing it to be executed on the blockchain. In relay transactions, this may be a relayer account rather than the end user, while in direct transactions, it represents the actual user or contract initiating the transaction.
TXVARIANTThe transaction’s information.
GAS_USEDNUMBERGas used for the transaction. This field represents the amount of computational resources consumed to execute the transaction. Gas is measured in units, and the actual cost is calculated by multiplying gas used by the gas price. In raw number format, to adjust divide by POW(10,12). Higher gas usage indicates more complex operations or larger computational requirements.
TRANSACTION_FEENUMBERTotal fee paid in NEAR to execute this transaction, which is a summation of all fees paid for actions and receipts within the transaction. In raw number format, to adjust divide by POW(10,24)
ATTACHED_GASNUMBERUnits of gas (figure is not decimal adjusted, 10^12) attached to the transaction (this is often higher than ‘Gas Used’).
TX_SUCCEEDEDBOOLEANBoolean indicating if the transaction was successful (rarely used, most tx succeed, it is receipts that can fail). This field tracks the overall success status of the transaction. While most transactions succeed at the transaction level, individual receipts within the transaction can still fail. This field is less commonly used for filtering since receipt-level success tracking provides more granular information about specific operations within the transaction.
FACT_TRANSACTIONS_IDTEXTA unique identifier for the record.
INSERTED_TIMESTAMPTIMESTAMP_NTZThe timestamp at which the record was initially created and inserted into this table.
MODIFIED_TIMESTAMPTIMESTAMP_NTZThe timestamp at which this record was last modified by an internal process.