Skip to main content
Schema: near.intents Table: fact_transactions Type: Base Table

​
What

​
Description

This table provides granular transaction-level data for all intent executions on the NEAR blockchain using the NEP245 (multi-token) standard combined with DIP4 (Decentralized Intent Protocol v4) metadata. Each row represents a single token transfer, mint, or burn operation within an intent execution, capturing the complete lifecycle of multi-token movements through the intent protocol. The table combines flattened NEP245 event data with enriched DIP4 metadata including referral information and fee collection details. This fact table serves as the foundational source for intent transaction analysis, providing the raw event data that powers higher-level analytics and easy views.

​
Key Use Cases

  • Token-level intent execution analysis and tracking individual token movements
  • Intent protocol volume analysis by counting distinct transactions and measuring token flow
  • Referral program attribution and effectiveness measurement
  • Fee revenue analysis when combined with fees_collected_raw metadata
  • Multi-token bundle analysis for complex intent executions involving multiple assets
  • Transaction success rate analysis using receipt_succeeded for operational metrics
  • Intent execution pattern analysis by examining log_event types (mt_transfer, mt_mint, mt_burn)

​
Important Relationships

  • Sources from silver.logs_nep245 for flattened NEP245 multi-token event data
  • Enriched with silver.logs_dip4 for referral tracking and fee collection metadata
  • Parent table for intents.ez_transactions which provides user-friendly aggregated intent views
  • Parent table for intents.ez_fees which extracts and analyzes fee collection details
  • Can be joined with core.fact_transactions using tx_hash for complete transaction context
  • Can be joined with core.fact_receipts using receipt_id for receipt execution details
  • Related to core.dim_ft_contract_metadata via token_id for token metadata enrichment

​
Commonly-used Fields

  • block_timestamp: Essential for time-series analysis and temporal pattern identification
  • tx_hash and receipt_id: Primary keys for joining with core transaction and receipt tables
  • token_id: Critical for identifying which multi-token assets are being transferred
  • amount_raw: Core field for volume analysis, must be decimal-adjusted using token metadata
  • log_event: Key field for filtering by operation type (mt_transfer, mt_mint, mt_burn)
  • owner_id, old_owner_id, new_owner_id: Critical for tracking token custody and building account balances
  • referral: Important for attributing transactions to referral sources and partners
  • fees_collected_raw: Used in revenue analysis and fee structure research
  • receipt_succeeded: Essential filter for excluding failed transactions from analytics

​
Columns

Column NameData TypeDescription
BLOCK_TIMESTAMPTIMESTAMP_NTZThe date and time at which the block began.
BLOCK_IDNUMBERThe height of the chain this block corresponds with.
TX_HASHTEXTUnique identifier (hash) of this transaction.
RECEIPT_IDTEXTThe identifying hash for a receipt.
RECEIVER_IDTEXTAccount reacting to the receipt from predecessorid, can be relay, a contract, or a user of a relay, etc. This field identifies the account that is processing the receipt and executing the associated action. In most cases, this is a smart contract that is being called, but it can also be a user account in relay transactions or the system account for certain operations. This differs from txreceiver and is specific to the receipt being processed.
PREDECESSOR_IDTEXTAccount that called the relevant receipt (often the same as tx_signer, but can be system as well). This field identifies the account that directly invoked the receipt being processed. In simple transactions, this is typically the same as the transaction signer. However, in cross-contract calls or system operations, this may be a different account or the system account. This is crucial for understanding the call chain and access control in NEAR’s execution model.
LOG_EVENTTEXTType of NEP245 event (e.g., mttransfer, mtburn, mt_mint)
LOG_INDEXNUMBERSequential index of the log entry within the receipt
LOG_EVENT_INDEXNUMBERPosition of the event in the log_data array
OWNER_IDTEXTAccount ID that owns the multi-token (NEP245) assets involved in the intent transaction. For mint events, this is the account receiving the newly created tokens. For burn events, this is the account whose tokens are being destroyed. This field is null for transfer events, which use oldownerid and newownerid instead. The owner_id is critical for tracking token custody and account balances in multi-token intent executions.
OLD_OWNER_IDTEXTSender account ID for transfer events
NEW_OWNER_IDTEXTReceiver account ID for transfer events
MEMOTEXTOptional log message within the transaction (often null). This field contains additional information or context about the transfer, such as transaction notes, reference numbers, or descriptive text. Memos are commonly used in cross-chain bridges, exchange deposits, or other scenarios where additional context is needed to identify or process the transfer. The memo field is optional and frequently null for standard transfers.
AMOUNT_INDEXNUMBERPosition of the amount in the flattened amounts array from the NEP245 event
AMOUNT_RAWTEXTUnadjusted amount of tokens as it appears on-chain (not decimal adjusted). This is the raw token amount before any decimal precision adjustments are applied. For example, if transferring 1 NEAR token, the amount_raw would be 1000000000000000000000000 (1e24) since NEAR has 24 decimal places. This field preserves the exact on-chain representation of the token amount for precise calculations and verification.
TOKEN_IDVARIANTThe identifier of the token being transferred or minted.
REFERRALTEXTID of the referring protocol, as extracted from the Receipt log.
FEES_COLLECTED_RAWVARIANTRaw JSON object containing fee information collected from the intent execution, as extracted from the DIP4 event log. This field contains the complete on-chain representation of fees charged by the intent protocol, formatted as a JSON object with token addresses as keys and unadjusted fee amounts as values. For example: {"nep141:wrap.near": "1232145523809524"} indicates fees collected in wrapped NEAR tokens. This field is null when no fees were collected or when fee information is not availab…
DIP4_VERSIONTEXTVersion of the DIP4 standard that emitted the log for this action.
GAS_BURNTNUMBERGas burned for the receipt action. This field represents the amount of computational resources consumed specifically for the receipt being processed. Gas burning is the mechanism by which NEAR charges for computational work, and this field tracks the exact amount burned for this particular receipt action. In raw number format with 16 decimal places, to adjust divide by POW(10,16) or multiply by 1e-16.
RECEIPT_SUCCEEDEDBOOLEANBoolean indicating whether the receipt was successfully processed. This field tracks the execution status of the receipt, which is crucial for understanding transaction outcomes. While most transactions succeed, individual receipts within a transaction can fail due to various reasons such as insufficient gas, contract errors, or invalid parameters. This field is essential for filtering successful operations and analyzing failure patterns.
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.
_INVOCATION_IDTEXTA job ID to identify the run that last modified a record.