Skip to main content
Schema: near.core Table: fact_token_transfers Type: Base Table

​
What

​
Description

This table contains all token transfers on the NEAR Protocol blockchain, capturing movements of native NEAR tokens, fungible tokens (NEP-141), and other token types across accounts and contracts. The data includes both direct transfers and complex token operations like minting, deposits, and liquidity operations. This table provides the foundation for understanding token economics, user behavior, and DeFi activity across the NEAR ecosystem, supporting comprehensive token flow analysis and balance tracking.

​
Key Use Cases

  • Token flow analysis and whale movement tracking
  • DeFi protocol volume analysis and liquidity monitoring
  • Token distribution analysis and holder behavior tracking
  • Cross-contract token movement analysis
  • Economic analysis of token transfers and value flows
  • Compliance and audit trail analysis for token movements
  • Token minting and burning pattern analysis

​
Important Relationships

  • Links to core.fact_transactions through tx_hash for transaction context
  • Connects to core.fact_blocks through block_id for temporal context
  • Provides transfer data for core.ez_token_transfers with enhanced metadata
  • Supports defi.ez_dex_swaps and defi.ez_bridge_activity through transfer events
  • Enables analysis in nft.ez_nft_sales through token payment flows
  • Powers stats.ez_core_metrics_hourly for aggregated transfer metrics

​
Commonly-used Fields

  • tx_hash: Essential for linking to transaction details and verification
  • block_timestamp: Primary field for time-series analysis and trend detection
  • from_address and to_address: Critical for flow analysis and network mapping
  • contract_address: Important for token-specific analysis and contract tracking
  • amount_unadj: Essential for value calculations and economic analysis
  • transfer_type: Important for categorizing different token standards
  • transfer_action: Critical for understanding the specific operation type

​
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.
RNNUMBERThe sequential index of an event within a transaction, combining the log index with any sub-indices from array processing. Used to maintain the correct order of events when multiple events are emitted in a single transaction.
CONTRACT_ADDRESSTEXTAccount 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.
FROM_ADDRESSTEXTThe address the sends the token.
TO_ADDRESSTEXTThe receiver of usn token.
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_UNADJTEXTAn unadjusted amount (of tokens, price, etc.) for the relevant record. This is the number as it appears on chain and is not decimal adjusted.
TRANSFER_TYPETEXTNature of the transfer. This field categorizes the type of token transfer being performed. Common values include “native” for raw NEAR token transfers, “nep141” for fungible token transfers following the NEAR token standard, and other protocol-specific transfer types. This helps distinguish between different token standards and transfer mechanisms used on the NEAR blockchain.
TRANSFER_ACTIONTEXTThe event that caused the transfer. Transfer: A standard transfer Action of tokens from one address to another. Deposit: A deposit Action of tokens into a contract. fttransfer: A transfer of tokens using the fttransfer method. fttransfercall: A transfer of tokens using the fttransfercall method. ftmint: A minting of tokens using the ftmint method. orderadded: An order being added to the orderbook. addliquidity: Adding liquidity to a pool. neardeposit: A deposit of NEAR tokens into the wrap.ne…
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_TOKEN_TRANSFERS_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.