Updates, latest day
countPyth price updates written on the selected chains on the latest complete day.
How many Pyth price updates land on each chain, for which feeds and who pays to pull them?
Pyth price updates pulled onto each chain: how many, for which feeds, who pulls them, the fees paid and how wide each feed's confidence is.
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.
How many updates land on each chain and for which feeds.
Pyth price updates written on the selected chains on the latest complete day.
Update fees paid to the Pyth contracts on the same day, valued at oracle prices.
Distinct Pyth feeds with at least one update on the selected chains that day.
Covered chains where at least one Pyth update landed in the selected period.
Pyth updates per day on each covered chain.
Each feed's symbol, chains, updates in the period, median time between updates and the apps that pull it most.
The apps that pull updates, what they pay and how tight each feed is.
Distinct contracts that submitted Pyth updates on covered chains in the period.
Share of updates in the period sent by keepers that refresh feeds on a schedule rather than by apps.
Updates submitted by each of the most active apps in the period.
Each feed's median confidence as a share of price in the period, with its widest band and when it occurred.
Pyth is a pull oracle. Exchanges, market makers and other publishers sign prices on Pythnet, Pyth's own appchain, which aggregates them into a price and a confidence interval for each feed. A Merkle root of those prices is signed through Wormhole, and an app that needs a price brings the signed update onto its own chain, pays a small fee and uses it in the same transaction.
Because updates are pulled, how often a price is refreshed on a chain depends on who uses it there. This dashboard counts the updates that land on each covered chain: which feeds are refreshed most, which apps pull them, what they pay and how wide each feed's confidence band is. Every update is read from the chain where it landed, with the transaction that carried it.
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
An oracle that does not write prices on-chain on its own schedule. Prices are signed elsewhere, and whoever needs one submits the signed update in a transaction, usually the same one that uses it. The user of the price pays for its delivery.
Publishers send prices to Pythnet, which aggregates them each slot. Wormhole guardians sign a Merkle root of all prices, and a service called Hermes serves updates with their proofs. An app passes an update to the Pyth contract on its chain, which checks the signatures and the proof before storing the price.
A band around each price that reflects how much publishers disagree and how uncertain the market is. A wide band means the aggregate price is less certain. Protocols can use it to widen safety margins, and the dashboard shows each feed's typical width.
The caller. An app or its users pay the update fee in the chain's native token, plus the gas of the transaction. Some feeds are also refreshed on a schedule by sponsored keepers, and the dashboard counts those updates separately.
Chainlink data feeds write new answers on-chain when a deviation threshold or heartbeat is reached, and apps read the stored price. Pyth publishes prices on Pythnet, and apps pull a signed update when they need one. Both are on-chain oracles; they differ in who triggers an update and who pays for it.
Each Chainlink price feed's last update and what triggered it, its heartbeat and deviation threshold, with stale feeds flagged right now.
EthereumArbitrumBase+4Daily and monthly trading volume and open interest on perpetual DEXs, venue by venue, with each venue's share and how it shifts.
Multi-chainHyperliquidArbitrum+2Every on-chain liquidation on lending markets and perp DEXs: collateral seized, debt repaid, the liquidator and the price at the block.
Multi-chainEthereumBase+2Messages 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+5Solana's throughput, daily transactions, fees, active wallets and failure rate, measured from every block and pinned to its slot.
SolanaDeFi value locked on each chain, counted once at oracle prices, with the chain ranking, Ethereum's share and the protocols behind it.
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.