Skip to main content
Schema: flow.defi Table: fact_bridge_activity Type: View

​
Description

Records all token bridge transactions to and from the Flow blockchain using supported bridge protocols (e.g., Blocto Teleport, Celer Bridge). Captures the full context of each cross-chain transfer, including source/destination addresses, token details, amounts, fees, and protocol metadata. Data is sourced from on-chain bridge events and normalized for analytics.

​
Key Use Cases

  • Analyze cross-chain token flows into and out of Flow
  • Monitor bridge usage, volume, and protocol adoption
  • Track user participation in bridging activity
  • Attribute fees and bridge revenue by protocol
  • Support compliance and risk monitoring for cross-chain transfers

​
Important Relationships

  • Linked to defi__ez_bridge_activity for enriched analytics (adds token symbols, USD values)
  • Can be joined with core__ez_token_transfers for end-to-end asset movement
  • Protocol attribution via platform and bridge_address fields
  • Token-level analytics via token_address and amount

​
Commonly-used Fields

  • tx_id: Unique transaction identifier for bridge event
  • block_timestamp: When the bridge transaction occurred
  • bridge_address: Contract address of the bridge protocol
  • token_address: Contract address of the bridged token
  • amount: Quantity of tokens bridged (decimal adjusted)
  • amount_fee: Fee charged by the bridge protocol
  • source_chain / destination_chain: Blockchains involved in the transfer
  • platform: Name of the bridge protocol

​
Columns

Column NameData TypeDescription
TX_IDTEXTThe 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_TIMESTAMPTIMESTAMP_NTZThe 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_HEIGHTNUMBERBlock 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_ADDRESSTEXTThe 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_ADDRESSTEXTThe 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.
AMOUNTFLOATThe 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_FEEFLOATThe 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.
SOURCE_ADDRESSTEXTThe 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_ADDRESSTEXTThe 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_CHAINTEXTThe 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_CHAINTEXTThe 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.
PLATFORMTEXTThe 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.
FACT_BRIDGE_ACTIVITY_IDTEXT
INSERTED_TIMESTAMPTIMESTAMP_NTZThe 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_TIMESTAMPTIMESTAMP_NTZThe 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.