Skip to main content
Schema: aptos.core Table: ez_native_transfers Type: View

​
Description

This table provides a simplified, flattened view of native token transfers on the Aptos blockchain, specifically focusing on APT token movements between accounts. The table applies specific business logic to identify genuine transfer pairs by requiring withdrawal events to occur immediately before deposit events with matching amounts, with exceptions for intermediate “CoinRegisterEvent” occurrences. This filtering ensures that only actual token transfers are captured, excluding other blockchain events that might appear as transfers but represent different operations.

​
Key Use Cases

  • Native APT token flow analysis and tracking across the network
  • Wallet-to-wallet transfer monitoring and pattern recognition
  • Network fee analysis and gas cost tracking for APT transfers
  • User behavior analysis for native token movements
  • Transfer volume analysis and network activity monitoring
  • Simplified transfer analysis without complex event parsing

​
Important Relationships

  • Complements the broader transfer analysis available in core.fact_transfers and core.ez_transfers
  • Provides simplified transfer data for analytics that don’t require complex event parsing
  • Supports native token-specific analysis separate from other token types
  • Enables straightforward sender-to-receiver transfer tracking

​
Commonly-used Fields

  • from_address: Essential for identifying transfer senders and outflow analysis
  • to_address: Critical for identifying transfer recipients and inflow analysis
  • amount: Transfer amount for value calculations and volume analysis
  • tx_hash: Important for linking to transaction details and verification
  • block_timestamp: Primary field for time-series analysis and trend detection
  • success: Transaction success status for filtering valid transfers

​
Columns

Column NameData TypeDescription
BLOCK_NUMBERNUMBERAlso known as block height. The block number indicates the position of a block in the blockchain, increasing sequentially after the addition of each new block.
Data type: Integer Example:
  • 12345678
  • 98765432
Business Context:
  • Primary identifier for ordering and filtering blockchain data chronologically.
  • Essential for block-level analysis and network growth tracking.
  • Enables correlation of transactions, transfers, and events to specific blocks. | | BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The date and time at which the block was produced on the Aptos blockchain.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Primary field for time-series analysis and temporal filtering of blockchain activity.
  • Essential for trend analysis, volume calculations, and historical comparisons.
  • Enables time-based grouping and aggregation for analytics and reporting. | | TX_HASH | TEXT | Transaction hash is a unique 66-character identifier that is generated when a transaction is executed on the Aptos blockchain.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Primary identifier for linking transaction data across all related tables.
  • Essential for transaction verification and blockchain explorer lookups.
  • Enables correlation of transfers, events, and state changes to specific transactions. | | VERSION | NUMBER | The version number, also known as the height, represents the sequential position of a transaction in the Aptos blockchain. The first transaction has a version of 0, and each subsequent transaction increments by 1.
Data type: Integer Example:
  • 0 (genesis transaction)
  • 12345678
  • 98765432
Business Context:
  • Unique identifier for ordering transactions chronologically across the entire blockchain.
  • Essential for transaction sequencing and version-based analysis.
  • Enables precise transaction tracking and blockchain state verification. | | SUCCESS | BOOLEAN | The boolean value indicating whether the transaction was successfully executed on the Aptos blockchain.
Data type: Boolean Example:
  • true (transaction succeeded)
  • false (transaction failed)
Business Context:
  • Essential for filtering successful transactions and analyzing failure rates.
  • Critical for accurate volume calculations and user experience analysis.
  • Enables debugging and error pattern recognition in transaction analysis. | | FROM_ADDRESS | TEXT | The account address that initiated the transfer, representing the sender of the tokens.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for transfer flow analysis and sender identification.
  • Critical for account activity tracking and transfer origin analysis.
  • Enables sender-based analytics and transfer flow reporting. | | TO_ADDRESS | TEXT | The account address that received the transfer, representing the recipient of the tokens.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for transfer flow analysis and recipient identification.
  • Critical for account activity tracking and transfer destination analysis.
  • Enables recipient-based analytics and transfer flow reporting. | | AMOUNT | NUMBER | The non-decimal adjusted amount of a token, representing the raw on-chain value before decimal precision is applied.
Data type: Decimal Example:
  • 1500000000000000000 (for 1.5 tokens with 18 decimals)
  • 1000000000000000000000 (for 1000 tokens with 18 decimals)
Business Context:
  • Preserves the exact on-chain representation for precise calculations and verification.
  • Essential for blockchain-level accuracy and cross-reference with external data sources.
  • Used when decimal precision needs to be maintained for technical analysis. | | TOKEN_ADDRESS | TEXT | The full address of the token on the Aptos blockchain, containing the account, module, and resource identifiers.
Data type: String Example:
  • 0x1::coin::AptosCoin (native APT token)
  • 0xf22bede237a07e121b56d91a491eb7bcdfd1f5907926a9e58338f964a01b17fa::coin::USDC
Business Context:
  • Primary identifier for filtering and grouping transactions by specific tokens.
  • Essential for DeFi analysis, token flow tracking, and protocol-specific analytics.
  • Enables correlation with token metadata for symbol and decimal information. | | EZ_NATIVE_TRANSFERS_ID | TEXT | The unique primary key identifier for each row in the table, ensuring data integrity and uniqueness.
Data type: String Example:
  • 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
Business Context:
  • Essential for data integrity and unique row identification.
  • Critical for join operations and data relationship management.
  • Enables precise data retrieval and referential integrity maintenance. | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the row was inserted into the table, representing when the data was first recorded.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for data lineage tracking and insertion timing analysis.
  • Critical for understanding data freshness and processing delays.
  • Enables data quality analysis and processing performance monitoring. | | MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | The UTC timestamp when the row was last modified, representing when the data was most recently updated.
Data type: Timestamp Example:
  • 2024-01-15 14:30:25.123456
Business Context:
  • Essential for data freshness analysis and update tracking.
  • Critical for understanding data modification patterns and change frequency.
  • Enables data quality monitoring and update performance analysis. |