Skip to main content
Schema: near.core Table: ez_token_transfers Type: Base Table This table records daily balances for NEAR Accounts, according to the parameters set by the Near teamā€™s balances indexer. More details around the source data can be found by reading about the NEAR Public Lakehouse on their documentation site: https://docs.near.org/tools/indexing. Please Note - Flipside does not index or curate the data in this table, we simply provide it as-is from the NEAR Public Lakehouse with a daily sync from the public access table located at bigquery-public-data.crypto_near_mainnet_us.ft_balances_daily.

ā€‹
Description

This table provides an enhanced view of all token transfers on the NEAR Protocol blockchain, combining raw transfer data with token metadata, pricing information, and decimal adjustments. The table includes both raw and adjusted amounts, USD values, and comprehensive token context, making it the primary table for token flow analysis and economic calculations. This easy view eliminates the need for complex joins and calculations, providing ready-to-use data for analytics, reporting, and business intelligence workflows.

ā€‹
Key Use Cases

  • Token flow analysis with accurate decimal-adjusted amounts and USD values
  • DeFi protocol volume analysis and liquidity monitoring
  • Token economics analysis and market impact assessment
  • Cross-token comparison and portfolio analysis
  • Whale movement tracking with value context
  • Token distribution analysis and holder behavior tracking
  • Economic impact analysis of token transfers and market movements

ā€‹
Important Relationships

  • Enhances core.fact_token_transfers with pricing and metadata from price.ez_prices_hourly
  • Combines token metadata from core.dim_ft_contract_metadata for complete token context
  • Supports defi.ez_dex_swaps with accurate token pricing and amounts
  • Enables defi.ez_bridge_activity with cross-chain value analysis
  • Powers stats.ez_core_metrics_hourly with aggregated transfer values
  • Provides foundation for all token-related analytics and reporting

ā€‹
Commonly-used Fields

  • amount_raw and amount_precise: Essential for accurate token amount analysis
  • amount_usd: Critical for economic analysis and value calculations
  • block_timestamp: Primary field for time-series analysis and trend detection
  • from_address and to_address: Important for flow analysis and network mapping
  • contract_address: Essential for token-specific analysis and filtering
  • symbol and decimals: Important for token identification and decimal handling
  • token_price: Useful for price trend analysis and market impact assessment

ā€‹
Columns

Column NameData TypeDescription
BLOCK_IDNUMBERThe height of the chain this block corresponds with.
BLOCK_TIMESTAMPTIMESTAMP_NTZThe date and time at which the block began.
TX_HASHTEXTUnique identifier (hash) of this transaction.
RECEIPT_IDTEXT
CONTRACT_ADDRESSTEXTThe address of the deployed contract for the token, nft, or other smart contract.
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_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.
AMOUNT_RAW_PRECISEFLOATDecimal adjusted amount of tokens (as float, rounded - use this generally). This field provides the token amount after applying the appropriate decimal precision adjustments based on the tokenā€™s decimal places. For example, if transferring 1 NEAR token, the amount_adj would be 1.0 after dividing the raw amount (1e24) by 10^24. This field is the most commonly used representation for token amounts in analytics and reporting as it provides human-readable values.
AMOUNT_PRECISETEXT
AMOUNTFLOAT
AMOUNT_USDFLOAT
DECIMALSNUMBER
SYMBOLTEXT
TOKEN_PRICEFLOAT
TOKEN_IS_VERIFIEDBOOLEANBoolean flag indicating whether the token or price record is verified by Flipsideā€™s crosschain curation process. Verified tokens are prioritized for analytics and are considered reliable for most use cases. Unverified tokens may be incomplete, deprecated, or experimental.
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.
  • ft_transfer: A transfer of tokens using the ft_transfer method.
  • ft_transfer_call: A transfer of tokens using the ft_transfer_call method.
  • ft_mint: A minting of tokens using the ft_mint method.
  • order_added: An order being added to the orderbook.
  • add_liquidity: Adding liquidity to a pool.
  • near_deposit: A deposit of NEAR tokens into the wrap.near contract.
  • near_withdraw: A withdrawal of NEAR tokens from the wrap.near contract. | | RECEIPT_SUCCEEDED | BOOLEAN | Boolean 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. | | EZ_TOKEN_TRANSFERS_ID | TEXT | A unique identifier for the record. | | ACTION_ID | TEXT | | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp at which the record was initially created and inserted into this table. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The timestamp at which this record was last modified by an internal process. |