| BLOCK_NUMBER | VARIANT | 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. |
| 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… |
| 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. |
| 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. |
| TX_TYPE | TEXT | The type of transaction executed on the Aptos blockchain, categorizing transactions by their purpose and origin. Data type: String Example: usertransaction (regular user-initiated transactions) blockmetadatatransaction (system transactions for block metadata) statecheckpoint_transaction (system transactions for state checkpoints) Business Context: Essential for filtering and categorizing different types of blockchain activity. Critical for separating user activity from system operations in an… |
| SENDER | TEXT | The address of the originator account that initiated and signed the transaction on the Aptos blockchain. Data type: String Example: 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef Business Context: Essential for user behavior analysis and wallet activity tracking. Critical for transaction attribution and sender-based analytics. Enables correlation with address labels for enhanced user profiling. |
| SIGNATURE | TEXT | A cryptographic signature generated by hashing the signing message with the client’s private key using the Ed25519 scheme on the Aptos blockchain. Data type: String Example: 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef Business Context: Essential for transaction verification and cryptographic security validation. Critical for authenticating transaction origin and preventing unauthorized transactions. Enables… |
| PAYLOAD | VARIANT | The data payload carried by a transaction, containing the specific instructions and parameters for the transaction execution. Data type: String (JSON) Example: {"function":"0x1::coin::transfer","typearguments":["0x1::aptoscoin::AptosCoin"],"arguments":["0x123...","1000000"]} Business Context: Essential for understanding the specific actions and parameters of transactions. Critical for transaction analysis and smart contract interaction tracking. Enables detailed transaction parsing and functi… |
| PAYLOAD_FUNCTION | TEXT | The specific function being called within the transaction payload, identifying the smart contract method to be executed. Data type: String Example: 0x1::coin::transfer 0x1::coin::register 0xf22bede237a07e121b56d91a491eb7bcdfd1f5907926a9e58338f964a01b17fa::coin::mint Business Context: Essential for categorizing transactions by function type and smart contract interaction. Critical for DeFi protocol analysis and function call pattern recognition. Enables transaction filtering and specific funct… |
| CHANGES | VARIANT | The state changes that were executed by the transaction, representing modifications to the blockchain’s global state. Data type: String (JSON) Example: [{"type":"write_resource","address":"0x123...","data":{"coin":{"value":"1000000"}}}] Business Context: Essential for understanding the impact and effects of transactions on blockchain state. Critical for state transition analysis and transaction effect tracking. Enables comprehensive transaction analysis and state modification monitoring. |
| EVENTS | VARIANT | The events that were emitted during transaction execution, representing notifications and state change announcements. Data type: String (JSON) Example: [{"type":"0x1::coin::DepositEvent","data":{"amount":"1000000","account":"0x123..."}}] Business Context: Essential for event-driven analytics and smart contract interaction monitoring. Critical for DeFi protocol analysis and event pattern recognition. Enables comprehensive transaction effect analysis and event correlation. |
| GAS_UNIT_PRICE | NUMBER | The cost per unit of gas, determining the transaction fee paid by the sender for each unit of computational resource consumed on the Aptos blockchain. Data type: Integer Example: 100 (100 octa per gas unit) 1000 (1000 octa per gas unit) Business Context: Essential for calculating total transaction fees and network economics analysis. Critical for understanding gas market dynamics and fee optimization. Enables cost analysis and user experience optimization. |
| GAS_USED | NUMBER | The amount of gas units consumed during the execution of a transaction on the Aptos blockchain. Data type: Integer Example: 1000 5000 15000 Business Context: Essential for gas fee calculations and network economics analysis. Critical for understanding transaction complexity and resource consumption. Enables optimization analysis and cost efficiency tracking. |
| MAX_GAS_AMOUNT | NUMBER | The maximum amount of gas units allocated for the execution of a transaction on the Aptos blockchain. Data type: Integer Example: 10000 50000 100000 Business Context: Essential for gas fee analysis and transaction cost optimization. Critical for understanding transaction complexity and resource requirements. Enables gas efficiency analysis and user experience optimization. |
| EXPIRATION_TIMESTAMP_SECS | NUMBER | The timestamp in seconds when the transaction ceases to be valid and can no longer be executed on the Aptos blockchain. Data type: Integer Example: 1705344000 (January 15, 2024 00:00:00 UTC) 1705430400 (January 16, 2024 00:00:00 UTC) Business Context: Essential for transaction validity analysis and expiration monitoring. Critical for understanding transaction lifecycle and time-based constraints. Enables analysis of transaction timing and network congestion patterns. |
| VM_STATUS | TEXT | The execution status of a transaction as reported by the Aptos Virtual Machine (VM), providing success confirmation or failure details. Data type: String Example: Executed successfully OUTOFGAS INSUFFICIENTBALANCE INVALIDARGUMENT Business Context: Essential for transaction success rate analysis and failure investigation. Critical for debugging transaction issues and understanding failure patterns. Enables user experience analysis and error pattern recognition. |
| STATE_CHANGE_HASH | TEXT | The cryptographic hash of the state changes, providing verification of the blockchain state modifications. Data type: String Example: 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef Business Context: Essential for state change verification and integrity validation. Critical for blockchain state consistency and change tracking. Enables state change analytics and integrity reporting. |
| ACCUMULATOR_ROOT_HASH | TEXT | The root hash of the Merkle accumulator, providing cryptographic proof of the blockchain’s state at a given point. Data type: String Example: 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef Business Context: Essential for blockchain state verification and integrity validation. Critical for consensus mechanism analysis and state synchronization. Enables verification of blockchain state consistency and security. |
| EVENT_ROOT_HASH | TEXT | The root hash of the event tree, providing cryptographic proof of all events emitted in the transaction. Data type: String Example: 0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef Business Context: Essential for event verification and integrity validation. Critical for event-driven analytics and event correlation analysis. Enables verification of event consistency and security. |
| FACT_TRANSACTIONS_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. |
