| TX_ID | TEXT | The 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. |
| BLOCK_TIMESTAMP | TIMESTAMP_NTZ | The 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. |
| BLOCK_HEIGHT | NUMBER | Block 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. |
| BRIDGE_ADDRESS | TEXT | The Flow contract address for the bridge protocol used to transfer tokens to or from the Flow blockchain. Data type: STRING. Identifies the specific bridge (e.g., Blocto Teleport, Celer) facilitating cross-chain transfers. Used for protocol attribution, analytics, and filtering bridge activity. Example: ‘0xabcdef1234567890’. Important for cross-chain analytics and monitoring bridge usage. |
| TOKEN_ADDRESS | TEXT | The 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. |
| TOKEN_SYMBOL | TEXT | Abbreviated symbol for the asset or token involved in the transaction. Data type: STRING. Used to quickly identify the type of asset (e.g., ‘FLOW’, ‘USDC’, ‘BLT’) in analytics, dashboards, and reporting. This field is essential for filtering, aggregating, and visualizing token-level activity, especially in bridge and DEX models. Example: ‘FLOW’ for Flow’s native token, ‘USDC’ for USD Coin. Important for token attribution, price lookups, and user-facing analytics. |
| AMOUNT | FLOAT | The 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. |
| AMOUNT_FEE | FLOAT | The fee amount deducted by the protocol, bridge, or contract as part of the transaction. Data type: NUMBER (decimal adjusted). Represents the cost paid by the user for using the service (e.g., bridge fee). Example: 0.1 (for 0.1 Flow tokens). Used for fee analysis, cost tracking, and protocol revenue analytics. |
| AMOUNT_USD | FLOAT | The value of the amount field denominated in US dollars, based on available pricing data at the time of the transaction. Data type: NUMBER (decimal adjusted). Used for financial analysis, protocol revenue tracking, and cross-chain comparisons. Example: 100.25 (for $100.25 USD). This field is essential for normalizing value across different tokens and blockchains, enabling USD-based analytics and dashboards. Important for DeFi analytics, cost analysis, and protocol performance measurement. |
| AMOUNT_FEE_USD | FLOAT | The value of the fee amount denominated in US dollars, based on available pricing data at the time of the transaction. Data type: NUMBER (decimal adjusted). Used for cost analysis, protocol revenue tracking, and financial reporting. Example: 0.25 (for $0.25 USD). Important for fee analytics and dashboards. |
| SOURCE_ADDRESS | TEXT | The Flow blockchain address of a wallet involved in the transaction (as sender, recipient, source, or destination). Data type: STRING. Used to identify participants in token transfers, swaps, or bridge activity. Example: ‘0x1cf0e2f2f715450’. Important for wallet attribution, cross-chain analytics, and user-level tracking. |
| DESTINATION_ADDRESS | TEXT | The Flow blockchain address of a wallet involved in the transaction (as sender, recipient, source, or destination). Data type: STRING. Used to identify participants in token transfers, swaps, or bridge activity. Example: ‘0x1cf0e2f2f715450’. Important for wallet attribution, cross-chain analytics, and user-level tracking. |
| SOURCE_CHAIN | TEXT | The name of the blockchain network involved in the transaction or address. Data type: STRING. This field is used to distinguish between different blockchains (e.g., ‘flow’, ‘ethereum’, ‘polygon’) in cross-chain analytics, bridge activity, and multi-chain protocols. It is essential for filtering, aggregating, and attributing activity to the correct network, especially in bridge and DeFi models where assets may move between chains. Example: ‘flow’ for native Flow transactions, ‘ethereum’ for bridged assets. Important for cross-chain analytics, protocol attribution, and ensuring accurate data segmentation in multi-chain environments. |
| DESTINATION_CHAIN | TEXT | The name of the blockchain network involved in the transaction or address. Data type: STRING. This field is used to distinguish between different blockchains (e.g., ‘flow’, ‘ethereum’, ‘polygon’) in cross-chain analytics, bridge activity, and multi-chain protocols. It is essential for filtering, aggregating, and attributing activity to the correct network, especially in bridge and DeFi models where assets may move between chains. Example: ‘flow’ for native Flow transactions, ‘ethereum’ for bridged assets. Important for cross-chain analytics, protocol attribution, and ensuring accurate data segmentation in multi-chain environments. |
| PLATFORM | TEXT | The name of the bridge protocol or service used to transfer tokens or assets between blockchains. Data type: STRING. This field identifies the specific bridge (e.g., ‘blocto’, ‘celer’) facilitating the cross-chain transfer. Used for protocol attribution, analytics, and filtering bridge activity. Example: ‘blocto’ for Blocto Teleport, ‘celer’ for Celer Bridge. Important for cross-chain analytics, protocol usage tracking, and understanding the flow of assets between networks. |
| EZ_BRIDGE_ACTIVITY_ID | TEXT | |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | The 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_TIMESTAMP | TIMESTAMP_NTZ | The 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. |
