near.core Table: fact_token_transfers Type: Base Table
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_transactionsthrough tx_hash for transaction context - Connects to
core.fact_blocksthrough block_id for temporal context - Provides transfer data for
core.ez_token_transferswith enhanced metadata - Supports
defi.ez_dex_swapsanddefi.ez_bridge_activitythrough transfer events - Enables analysis in
nft.ez_nft_salesthrough token payment flows - Powers
stats.ez_core_metrics_hourlyfor aggregated transfer metrics
Commonly-used Fields
tx_hash: Essential for linking to transaction details and verificationblock_timestamp: Primary field for time-series analysis and trend detectionfrom_addressandto_address: Critical for flow analysis and network mappingcontract_address: Important for token-specific analysis and contract trackingamount_unadj: Essential for value calculations and economic analysistransfer_type: Important for categorizing different token standardstransfer_action: Critical for understanding the specific operation type
Columns
| Column Name | Data Type | Description |
|---|---|---|
| BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The date and time at which the block began. |
| BLOCK_ID | NUMBER | The height of the chain this block corresponds with. |
| TX_HASH | TEXT | Unique identifier (hash) of this transaction. |
| RECEIPT_ID | TEXT | The identifying hash for a receipt. |
| RN | NUMBER | The 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_ADDRESS | TEXT | Account 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_ADDRESS | TEXT | The address the sends the token. |
| TO_ADDRESS | TEXT | The receiver of usn token. |
| MEMO | TEXT | Optional 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_UNADJ | TEXT | An 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_TYPE | TEXT | Nature 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_ACTION | TEXT | The 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. | | FACT_TOKEN_TRANSFERS_ID | TEXT | A unique identifier for the record. | | 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. |