Skip to main content
Dune’s bridge tables track cross-chain token transfers across 41 EVM chains, capturing deposit events on the source chain and withdrawal events on the destination chain, then matching them into complete bridge flows.
Maintained by: Dune · Refresh: ~30 min · Chains: 41 EVM chains

Get This Data

Access bridge data via API, Datashare, or the Dune App.

​
Available Tables

bridges_evms.flows

Matched deposit-withdrawal pairs showing complete bridge transfers

bridges_evms.deposits

Individual deposit events on source chains

bridges_evms.withdrawals

Individual withdrawal events on destination chains

​
When to Use These Tables

  • Track cross-chain capital flows between L1s and L2s
  • Monitor bridge protocol volumes and market share
  • Analyze net inflows/outflows for specific chains
  • Identify bridge usage patterns for wallets or tokens
  • Build cross-chain flow dashboards for chain ecosystem teams

​
Coverage

Abstract, Apechain, Arbitrum, Avalanche C-Chain, Base, Berachain, Blast, BNB Chain, Bob, Boba, Celo, Corn, Ethereum, Fantom, Flare, Gnosis, HyperEVM, Ink, Kaia, Katana, Lens, Linea, Mantle, Nova, opBNB, Optimism, Plasma, Plume, Polygon, Ronin, Scroll, Sei, Sonic, Sophon, Story, Taiko, Unichain, Worldchain, zkEVM, zkSync, Zora
Protocols: All major bridge protocols with decoded contracts on Dune. Use SELECT DISTINCT bridge_name FROM bridges_evms.deposits for the current list.

​
Query Performance

Filter on block_date or block_time ranges. For chain-specific analysis, also filter on deposit_chain or withdrawal_chain. 
-- ✅ Good: time-bounded with chain filter
SELECT * FROM bridges_evms.deposits
WHERE deposit_chain = 'ethereum'
  AND block_date >= DATE '2025-01-01'

-- ❌ Slow: unbounded scan
SELECT * FROM bridges_evms.flows
WHERE bridge_name = 'across'

​
Methodology

Bridge tables are maintained by Dune (source code). The system works in three stages: (1) deposits decodes deposit events on source chains, enriched with token metadata and USD pricing; (2) withdrawals decodes withdrawal events on destination chains; (3) flows joins deposits and withdrawals on bridge_transfer_id to produce matched pairs representing complete cross-chain transfers. Not all deposits have matching withdrawals (and vice versa), as matching depends on both chains being indexed and the bridge protocol emitting linkable identifiers.

​
Example Queries

Daily bridge volume by destination chain (last 30 days): 
SELECT
  date_trunc('day', deposit_block_time) AS day,
  withdrawal_chain,
  SUM(amount_usd) AS bridge_volume_usd,
  COUNT(*) AS num_transfers
FROM bridges_evms.flows
WHERE deposit_block_time >= NOW() - INTERVAL '30' DAY
GROUP BY 1, 2
ORDER BY 1 DESC, 3 DESC
Net flows for a specific chain: 
WITH inflows AS (
  SELECT SUM(deposit_amount_usd) AS total_in
  FROM bridges_evms.deposits
  WHERE withdrawal_chain = 'base'
    AND block_date >= DATE '2025-01-01'
),
outflows AS (
  SELECT SUM(deposit_amount_usd) AS total_out
  FROM bridges_evms.deposits
  WHERE deposit_chain = 'base'
    AND block_date >= DATE '2025-01-01'
)
SELECT
  i.total_in,
  o.total_out,
  i.total_in - o.total_out AS net_flow
FROM inflows i, outflows o
  • cex.flows — For tracking flows to/from centralized exchanges
  • tokens.transfers — Raw token transfer events (bridges are a subset of all transfers)

Enterprise Data Solutions

Need custom bridge datasets or additional chain coverage? Talk to our enterprise team.

Build Custom Models

Build private cross-chain flow pipelines with the dbt Connector.