Skip to main content
Schema: flow.core Table: ez_token_transfers Type: Base Table

​
Description

This table records all token transfers on the Flow blockchain, capturing both native and fungible token movements between accounts. Each row represents a single transfer event, including metadata such as transaction ID, block height, timestamp, sender, recipient, token contract, and amount. The table provides a normalized, analytics-ready view of token flows, supporting financial analysis, wallet tracking, and protocol monitoring.

​
Key Use Cases

  • Analyzing token flow and wallet activity across the Flow ecosystem
  • Measuring protocol, dApp, or user-level token volumes and trends
  • Supporting DeFi analytics, whale tracking, and compliance monitoring
  • Building dashboards for token distribution, holder analysis, and transfer patterns

​
Important Relationships

  • Derived from core.fact_events by extracting token transfer events and normalizing fields
  • Can be joined to core.dim_labels via sender or recipient for entity enrichment
  • Token contract field can be joined to contract label tables for protocol-level analytics
  • Used as a source for curated gold models in DeFi, rewards, and NFT analytics

​
Commonly-used Fields

  • tx_id: Unique identifier for the transaction containing the transfer
  • sender: The Flow address sending tokens
  • recipient: The Flow address receiving tokens
  • token_contract: The contract address of the transferred token
  • amount: The quantity of tokens transferred (decimal adjusted)
  • block_timestamp: Used for time-series and trend analysis

​
Columns

Column NameData TypeDescription
BLOCK_HEIGHTNUMBERBlock height is the unique, sequential integer assigned to each block as it is added to the Flow blockchain. It serves as the primary identifier for block ordering and is used to reference the position of a block within the chain. Data type: INTEGER. Block height is essential for joining block, transaction, and event tables, and for analyzing blockchain growth over time. For example, block height 100,000 refers to the 100,000th block produced on Flow. This field is critical for time-series analytics, chain reorganization analysis, and historical state reconstruction.
BLOCK_TIMESTAMPTIMESTAMP_NTZThe timestamp (in UTC) when the block or transaction was recorded on the Flow blockchain. Data type: TIMESTAMP_NTZ. This field is essential for time-series analysis, ordering events, and joining with other tables by time. For example, a block with block_height 100,000 may have a block_timestamp of ‘2023-01-01 12:00:00’. Used for analytics on network activity, transaction throughput, and historical state reconstruction.
TX_IDTEXTThe unique identifier (hash) for a transaction on the Flow blockchain. Data type: STRING. Each transaction is assigned a cryptographic hash that ensures its uniqueness and immutability. Used for joining transaction data across tables, tracing transaction execution, and verifying transaction integrity. Example: ‘e3f1c2d4…’. Essential for transaction-level analytics, debugging, and cross-referencing with block and event data.
SENDERTEXTAddress sending the transferred token.
RECIPIENTTEXTAddress receiving the transferred token.
TOKEN_CONTRACTTEXTThe Flow contract address for the token involved in the transaction. Data type: STRING. Used to identify the specific fungible or non-fungible token being transferred, swapped, or bridged. Example: ‘A.1654653399040a61.FlowToken’. Important for token-level analytics, filtering, and protocol attribution.
AMOUNTFLOATThe quantity of points, tokens, or assets transferred in the transaction. Data type: NUMBER (decimal adjusted). This field represents the amount moved between accounts, earned through activities, or spent on rewards. Used for financial analysis, volume tracking, reward program analytics, and transaction value calculations. Example: 100.0 for 100 reward points, 50.5 for 50.5 Flow tokens. Critical for reward program performance analysis, user engagement tracking, and maintaining accurate transaction records.
TX_SUCCEEDEDBOOLEANTransaction status, if it succeeded or failed.
EZ_TOKEN_TRANSFERS_IDTEXTpk_id is a surrogate primary key, uniquely generated for each row in the table. Data type: STRING or INTEGER (implementation-specific). This field ensures every record is uniquely identifiable, even if the source data lacks a natural primary key. Used for efficient joins, deduplication, and as a reference in downstream models. Example: an auto-incremented integer or a UUID string. Essential for maintaining data integrity and supporting dbt tests for uniqueness.
INSERTED_TIMESTAMPTIMESTAMP_NTZThe UTC timestamp when the record was first created and inserted into this table. Data type: TIMESTAMP_NTZ. Used for ETL auditing, tracking data freshness, and identifying when data was loaded or updated in the analytics pipeline. Example: ‘2023-01-01 12:00:00’. This field is critical for monitoring data latency, troubleshooting ETL issues, and supporting recency tests in dbt.
MODIFIED_TIMESTAMPTIMESTAMP_NTZThe UTC timestamp when this record was last updated or modified by an internal ETL or dbt process. Data type: TIMESTAMP_NTZ. Used for change tracking, ETL auditing, and identifying the most recent update to a record. Example: ‘2023-01-02 15:30:00’. This field is important for troubleshooting data issues, monitoring pipeline health, and supporting recency or freshness tests in dbt.