| BLOCK_NUMBER | NUMBER | Also 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… |
| 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. |
| EVENT_INDEX | NUMBER | Unique identifier for an event within a transaction, representing the sequential order of events emitted during transaction execution. Data type: Integer Example: 0 (first event in transaction) 1 (second event in transaction) 5 (sixth event in transaction) Business Context: Essential for determining the chronological order of events within a transaction. Critical for event correlation and transaction flow analysis. Enables precise event sequencing and debugging of complex transactions. |
| CREATION_NUMBER | NUMBER | Creation number corresponding to the event stream originating from the given account, representing the order of events emitted by that account. Data type: Integer Example: 0 (first event from account) 5 (6th event from account) 25 (26th event from account) Business Context: Essential for event ordering and account event stream analysis. Critical for event correlation and account activity tracking. Enables event-based analytics and account behavior analysis. |
| TRANSFER_EVENT | TEXT | The type of transfer event, indicating whether tokens were withdrawn from or deposited to an account. Data type: String Example: WithdrawEvent DepositEvent Business Context: Essential for categorizing transfer direction and flow analysis. Critical for understanding token movement patterns and account behavior. Enables transfer type analytics and flow direction reporting. |
| ACCOUNT_ADDRESS | TEXT | The top-level account address associated with this event, representing the primary account involved in the event. Data type: String Example: 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef Business Context: Essential for identifying the primary account involved in events. Critical for account-based event analysis and activity tracking. Enables account-centric analytics and event correlation. |
| 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 maintai… |
| 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 dec… |
| IS_FUNGIBLE | BOOLEAN | Boolean indicating whether the transfer was conducted using the legacy coin transfer mechanism (simpler, original method) or the fungibleasset module (newer, more flexible system for managing fungible assets). Data type: Boolean Example: true (uses fungibleasset module) false (uses legacy coin transfer mechanism) Business Context: Essential for understanding transfer mechanism evolution and compatibility. Critical for protocol analysis and transfer method categorization. Enables mechanism-bas… |
| STORE_ADDRESS | TEXT | STORE_ADDRESS column |
| FACT_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. |
