GMP calls
countContractCall and ContractCallWithToken events on covered gateways in the selected period.
How many cross-chain calls and token transfers go through Axelar, on which routes and who signs them?
Cross-chain calls and token transfers over Axelar by route, the gas prepaid for them and the validator set that signs for the gateways.
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.
GMP calls by route, with time to approval and gas prepaid.
ContractCall and ContractCallWithToken events on covered gateways in the selected period.
Share of calls in the period that also carried tokens.
The median time from the call block to the approval block on the destination gateway.
Gas paid to the gas service for calls in the period, valued at oracle prices.
GMP calls each day, split by source chain.
Each route's calls, calls with tokens, gas prepaid and median time to approval and to execution.
Interchain Token Service transfers and the validator set that signs.
Tokens registered or deployed through the Interchain Token Service on covered chains.
Value moved through the Interchain Token Service in the period, valued at oracle prices.
Value moved through the token service by each of the most used tokens in the period.
Each Axelar validator's voting power, its share of the set and the connected chains it runs nodes for, at the latest day's end.
Axelar is a proof-of-stake chain that connects other chains through gateway contracts. A contract on one chain calls its local gateway. Axelar's validators, who run nodes for the connected chains, vote that the call happened, and the validator set signs an approval that the destination gateway accepts, after which the destination contract executes it. This is General Message Passing, or GMP.
Tokens move the same way. The Interchain Token Service lets an issuer make a token available on many chains, either by locking it on its home chain and minting elsewhere or by burning and minting. This dashboard reads calls, approvals and executions from the gateways, transfers from the token service and the validator set from the Axelar chain itself.
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 proof-of-stake blockchain built with the Cosmos SDK that connects many chains. Its validators watch the connected chains, vote on what happened there and jointly sign approvals that the gateway contracts on each chain accept.
A way for a contract on one chain to call a contract on another. The sender calls the gateway with a destination and a payload and prepays gas to the gas service, and the destination contract receives the payload once Axelar approves it.
Axelar's framework for tokens that live on many chains. An issuer can register an existing token, locked on its home chain and minted elsewhere, or deploy a new interchain token that is burned and minted as it moves.
Axelar's validators, who stake AXL and run nodes for the chains Axelar connects. A cross-chain call is approved only after enough of them, weighted by stake, vote that it happened and sign the approval. The dashboard shows the set and its weights.
An extension that lets new chains connect to Axelar without waiting for its validators to add support: an integrator deploys contracts and runs verifiers that confirm messages from the new chain.
Messages dispatched and delivered over Hyperlane, Warp Route token transfers and the security module each recipient relies on.
Multi-chainEthereumArbitrum+5Messages 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 and token value sent over Chainlink CCIP lane by lane, with delivery times, fee tokens and how close pools are to their limits.
Multi-chainEthereumArbitrum+5Each major LayerZero-bridged token, route by route: which verifiers check its messages, how many must agree and whether one alone suffices.
Multi-chainEthereumArbitrum+5How much volume intent-based bridges and swaps fill, which solvers and relayers fill it and how long a fill takes from deposit to delivery.
Multi-chainEthereumBase+2Major 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.