Transfers

One row per cross-chain transfer, with the sending and arriving legs matched onto the same row. transfer_amount_usd holds the transfer valued once in USD, taken from whichever leg the row is anchored on.

Columns

Column	Type	Description
`block_timestamp`	`TIMESTAMP`	Time of the block the row is anchored on: the sending leg’s block, or the arriving leg’s on a row anchored there. Partition column.
`project_id`	`STRING`	Project operating the bridge.
`product_id`	`STRING`	Version of the bridge within that project.
`app_id`	`STRING`	Bridge app the transfer went through: `chainlink-ccip`, `circle-cctp-v1`, `circle-cctp-v2`, `layerzero-v1` or `layerzero-v2`.
`match_key`	`STRING`	Identifier the two legs are paired on, published by the bridge itself, such as LayerZero’s GUID or CCIP’s message id.
`match_method`	`STRING`	How the two legs were paired. Reads `exact` on a row with both legs.
`latency_seconds`	`INT64`	Seconds the transfer took: the arriving block’s time minus the sending block’s. Populated on a row with both legs.
`unmatched_reason`	`STRING`	Why a row has a single leg. On a row anchored on its sending leg it reads `source_key_missing`, `destination_chain_not_indexed`, `destination_leg_not_decoded` or `destination_pending_or_failed`; on one anchored on its arriving leg, `destination_key_missing`, `source_chain_not_indexed`, `source_leg_not_decoded` or `source_leg_missing`.
`intermediary_address`	`STRING`	Address of the relayer that relayed the message, on bridges that name one.
`source_chain_id`	`STRING`	Chain the transfer left. Clustering column.
`source_transaction_hash`	`STRING`	Hash of the transaction the sending leg was in.
`source_log_index`	`INT64`	Position of the sending event within its block.
`source_sub_log_index`	`INT64`	Which token inside a sending event that moved more than one, counting up from zero. CCIP sending legs are the ones that move more than one.
`source_block_timestamp`	`TIMESTAMP`	Time of the block the transfer left in.
`source_block_number`	`INT64`	Number of that block.
`source_sender_address`	`STRING`	Address that sent the transfer.
`source_recipient_address`	`STRING`	Address the sending leg names as the recipient.
`source_token_address`	`STRING`	Token contract on the chain the transfer left.
`source_token_id`	`STRING`	That token’s key in `dimensions.tokens`.
`source_bridge_contract_address`	`STRING`	Bridge contract the sending event came from.
`source_amount_raw`	`BIGNUMERIC`	Amount leaving, in the token’s smallest units, before decimals are applied.
`destination_chain_id`	`STRING`	Chain the transfer arrived on. Clustering column.
`destination_transaction_hash`	`STRING`	Hash of the transaction the arriving leg was in.
`destination_log_index`	`INT64`	Position of the arriving event within its block.
`destination_block_timestamp`	`TIMESTAMP`	Time of the block the transfer arrived in.
`destination_block_number`	`INT64`	Number of that block.
`destination_sender_address`	`STRING`	Sender named on the arriving leg.
`destination_recipient_address`	`STRING`	Address that received the transfer.
`destination_token_address`	`STRING`	Token contract on the chain the transfer arrived on.
`destination_token_id`	`STRING`	That token’s key in `dimensions.tokens`.
`destination_bridge_contract_address`	`STRING`	Bridge contract the arriving event came from.
`destination_amount_raw`	`BIGNUMERIC`	Amount arriving, in the token’s smallest units, before decimals are applied.
`source_transfer_amount`	`FLOAT64`	Amount leaving, in whole token units.
`source_transfer_amount_usd`	`FLOAT64`	Amount leaving, in USD, measured on the sending leg.
`destination_transfer_amount`	`FLOAT64`	Amount arriving, in whole token units. On bridges whose arrival event omits the amount, such as CCIP, this takes the sending leg’s amount.
`destination_transfer_amount_usd`	`FLOAT64`	Amount arriving, in USD, measured on the arriving leg, with the same fallback.
`transfer_amount`	`FLOAT64`	The transfer counted once, in whole token units: the sending leg’s amount, or the arriving leg’s on a row anchored there.
`transfer_amount_usd`	`FLOAT64`	The transfer counted once, in USD. Sum this column for total volume; the two directional columns describe the same value from opposite ends.

Sample queries

This table is large and split by day. Bound block_timestamp and filter source_chain_id on every query, or you read the whole table and the whole table is billed to you.

One day, one chain
Daily volume by app
Routes by volume
Latency by app

source_chain_id is a clustering column alongside the partition, so a single chain over one day reads a fraction of that day. Amounts here are the sending leg’s own, in the token’s units and in USD.

select
    transfers.block_timestamp,
    transfers.app_id,
    transfers.source_transaction_hash,
    transfers.destination_chain_id,
    transfers.source_token_id,
    transfers.source_transfer_amount,
    transfers.source_transfer_amount_usd
from `facts_bridge_tokens.transfers` as transfers
where transfers.source_chain_id = 'ethereum'
  and transfers.block_timestamp >= timestamp('2026-08-20')
  and transfers.block_timestamp < timestamp('2026-08-21')
order by transfers.source_transfer_amount_usd desc
limit 100

transfer_amount_usd takes the sending leg’s value, or the arriving leg’s on a row anchored there, so each transfer contributes once to the total. Both bounds on block_timestamp are what hold the scan to the window.

select
    timestamp_trunc(transfers.block_timestamp, day) as day,
    transfers.app_id,
    sum(transfers.transfer_amount_usd) as volume_usd
from `facts_bridge_tokens.transfers` as transfers
where transfers.block_timestamp >= timestamp('2026-08-01')
  and transfers.block_timestamp < timestamp('2026-08-08')
group by day, transfers.app_id
order by day, volume_usd desc

A route is the pair source_chain_id and destination_chain_id, both filled in on a row with two legs, and both are clustering columns. Ranking on transfer_amount_usd keeps each transfer to one route.

select
    transfers.source_chain_id,
    transfers.destination_chain_id,
    sum(transfers.transfer_amount_usd) as volume_usd
from `facts_bridge_tokens.transfers` as transfers
where transfers.block_timestamp >= timestamp('2026-08-01')
  and transfers.block_timestamp < timestamp('2026-08-08')
  and transfers.destination_chain_id is not null
group by transfers.source_chain_id, transfers.destination_chain_id
order by volume_usd desc
limit 25

latency_seconds is filled in on a row with both legs, so the average runs over the transfers whose arrival was found. The median is the more useful figure here: a long tail of slow arrivals pulls the mean up.

select
    transfers.app_id,
    round(avg(transfers.latency_seconds)) as mean_seconds,
    approx_quantiles(transfers.latency_seconds, 100)[offset(50)] as median_seconds
from `facts_bridge_tokens.transfers` as transfers
where transfers.block_timestamp >= timestamp('2026-08-01')
  and transfers.block_timestamp < timestamp('2026-08-02')
  and transfers.latency_seconds is not null
group by transfers.app_id
order by median_seconds

Overview

Popular datasets

Market verticals

Chain ecosystems

Core entities

Columns

Sample queries

​Columns

​Sample queries

Columns

Sample queries