Skip to main content
crosschain.bridges.matched_transfers pairs outbound bridge transactions on the source chain with their corresponding inbound delivery transactions on the destination chain. Each row represents a single confirmed end-to-end bridge transfer with both legs reconciled, along with hydrated token amounts, USD values, spread, and latency metrics.
Only matched pairs are included — outbound transactions that could not be matched to an inbound delivery (e.g. in-flight, refunded, or missing data) are excluded from this view. Query the per-direction tables (crosschain.bridges.bridges_outbound_transfers, crosschain.bridges.messaging_protocols_outbound_messages, crosschain.bridges.bridge_aggregators_outbound_transfers) if you need to see unmatched outbound activity.

Protocol Coverage

Matched transfers are produced for 17 bridge and messaging protocols, grouped by bridge_type:

Match Types

The match_type column describes how the outbound and inbound legs were paired:
  • exact: deterministic join on a protocol-native identifier (e.g. deposit_id, LayerZero guid, CCTP nonce, Wormhole sequence, Axelar command_id, order hash).
  • composite: joined on a combination of recipient address, token, amount, and a source→destination chain pair within a time window, for protocols where no single global identifier is emitted on both sides.

Spread & Latency

  • spread_percentage = (outbound_usd_amount - inbound_usd_amount) / outbound_usd_amount * 100. Nulled out when either USD amount is missing, the outbound amount is zero, or the absolute spread exceeds 25% (usually a sign of a mispriced token or mismatched pair).
  • latency_seconds = seconds elapsed from outbound to inbound block timestamp. Can be negative for intent-based protocols (Across, DeBridge DLN, Mayan Swift) where fillers front funds on the destination chain before the source-side transaction is finalized. Nulled out when outside the -3600s to 86400s range.

Sample Queries

Average bridge latency and spread by protocol over the last 7 days.
Top cross-chain user flows (source → destination) by matched volume.

Table Columns

Unique key: unique_id