Messages delivered
countCCIP messages executed on covered destination chains over the selected period.
How many messages and how much token value move over Chainlink CCIP, on which lanes and how fast are they delivered?
Messages and token value sent over Chainlink CCIP lane by lane, with delivery times, fee tokens and how close pools are to their limits.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
Messages and token value by lane, with delivery times.
CCIP messages executed on covered destination chains over the selected period.
Token value carried by those messages, valued at oracle prices at the send block.
Source and destination pairs with at least one delivered message in the period.
The median time from send block to execution block across messages in the period.
CCIP messages sent each day, split by source chain.
Each lane's messages, token value, median delivery time and the share of fees paid in LINK over the period.
Which tokens cross over CCIP, through which pools and how much capacity each lane has left.
Tokens with at least one registered CCIP token pool on covered chains.
Token pool lanes whose available capacity is below a fifth of their maximum at the latest block.
Token value moved in the period through lock-and-release pools and through burn-and-mint pools.
Each token's pool type, chains, rate limit per lane, capacity left now and value moved in the period.
Chainlink's Cross-Chain Interoperability Protocol, CCIP, carries messages and tokens between chains. A message leaves through the source chain's OnRamp, a committing oracle network posts a Merkle root of messages to the destination, a separate Risk Management Network checks it and an executing network delivers it through the OffRamp. This dashboard follows each message from send to delivery.
Tokens move through token pools that either lock and release a token or burn and mint it, and each pool sets rate limits per lane that cap how much can cross in a window. Under the Cross-Chain Token standard, issuers deploy and control their own pools. The dashboard shows the value moving on each lane, which tokens use which pool type and how much capacity each lane has left.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →Read from chain state and history
A protocol for sending messages, tokens or both between blockchains, run by Chainlink oracle networks. An app calls the CCIP router on the source chain and pays a fee, and the message or tokens arrive on the destination chain, where a receiver contract can act on them.
A committing oracle network posts a Merkle root of messages from the source chain to the destination. A separate Risk Management Network, built and run independently, checks that root, and only then can an executing network deliver the messages against it. A message that fails either check is not executed.
A way for token issuers to make their token transferable over CCIP on their own terms: they deploy a token pool on each chain, choose lock and release or burn and mint and keep control of the pools and their rate limits.
Caps set per token pool and per lane on how much of a token can leave or arrive in a window. Each works like a bucket that refills over time, so a sudden drain through one lane is limited even if something else fails.
CCIP waits for the source chain to reach finality before a message is committed, so delivery time depends mostly on the source chain. The dashboard shows the median per lane, measured from the send block to the execution block.
Each Chainlink price feed's last update and what triggered it, its heartbeat and deviation threshold, with stale feeds flagged right now.
EthereumArbitrumBase+4Each major LayerZero-bridged token, route by route: which verifiers check its messages, how many must agree and whether one alone suffices.
Multi-chainEthereumArbitrum+5Whether each bridged token's supply on other chains is matched by tokens locked on its home chain, with every gap shown.
Multi-chainEthereumBase+4Messages and token value moving over Wormhole by route and product, with the guardian set behind them and the rate limits on NTT tokens.
Multi-chainEthereumSolana+5Messages dispatched and delivered over Hyperlane, Warp Route token transfers and the security module each recipient relies on.
Multi-chainEthereumArbitrum+5Major chains ranked by the fees users paid last month, split into fees burned and fees paid to validators, beside new issuance.
Multi-chainEthereumSolana+3Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.