Oracle price
USDThe asset's oracle price at the snapshot block, the line the heatmap is centered on.
Dashboard · VantagePlanned
Liquidation Heatmap from On-Chain Positions
At which BTC and ETH prices would open on-chain positions be liquidated, and how much collateral sits at each level?
Where open BTC and ETH positions on perpetual exchanges and lending markets would be liquidated, computed from the positions themselves.
ShareEmail it
Blueprint
What the dashboard will show.
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.
Heatmap
Liquidation levels around the current price for the chosen asset.
Long collateral below price
USDCollateral of long and long-like positions whose liquidation price lies within the selected range below the current price.
Short collateral above price
USDCollateral of short and short-like positions whose liquidation price lies within the selected range above the current price.
Largest nearby cluster
USDThe price band within the range that holds the most collateral at risk, with its distance from the current price.
Liquidation heatmap
USDCollateral at risk by price band and venue across the selected range, with the current price marked.
Cumulative liquidations by price
USDCollateral that would be liquidated as price moves away from the current level, summed band by band in each direction.
Positions
The positions behind the levels, by venue.
Positions counted
countOpen BTC or ETH positions included in the snapshot across every covered venue.
Largest venue's share
%Share of the collateral at risk within the range that is held on its largest venue.
At risk by venue
USDCollateral at risk in the range per venue, split into longs and shorts.
Positions nearest liquidation
The largest positions within the range, with venue, side, collateral, debt or size, liquidation price and distance from the current price.
- Asset
- BTC or ETH
- Price range
- Within a tenth, a quarter or half of the current price
About
What it answers, and for whom.
A liquidation heatmap shows the prices at which leveraged positions would be forced closed. When many positions share a liquidation price, a move to that level can set off a chain of forced selling or buying, so traders and risk teams watch where those clusters sit.
This heatmap is computed from open positions read from chain state at a pinned block. Hyperliquid reports each position's liquidation price; for Aave, Morpho Blue and Compound, the price at which each borrower's health would fall below the liquidation line is solved from their collateral, their debt and the market's liquidation threshold.
Read it as a map of where leverage sits right now. Positions open, close and add collateral every block, so each snapshot names its block and its levels move as soon as borrowers act.
Method
How it will be measured.
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 →- Hyperliquid BTC and ETH perpetual positions come from its clearinghouse state per account, each with its size, side, margin and the liquidation price the venue reports.
- Aave v3 borrowers are enumerated from Supply, Borrow, Repay and Withdraw events; getUserAccountData() and each reserve's liquidation threshold give the price at which the health factor reaches one.
- Morpho Blue positions use each market's LLTV and oracle, and Compound v3 positions use liquidateCollateralFactor, with the same solve for the liquidation price.
- For a position with several collateral assets, the level is the BTC or ETH price that alone would trigger liquidation, holding the other prices at their oracle values at the snapshot block.
- Collateral at each level is bucketed into price bands and summed in USD at the snapshot's oracle prices; every band opens to the positions in it.
The data it needs
Read from chain state and history
- lending_markets_dailyTo buildLending marketsSupply, borrow, utilization and rates per lending market (Aave, Morpho, Spark, Compound, Euler and others) at day end.
- perps_markets_dailyTo buildOn-chain perpetualsVolume, open interest, funding rates and fees per market on on-chain perpetual exchanges, per day.
- liquidationsTo buildLiquidationsEvery liquidation on major lending markets and perp venues: collateral seized, debt repaid, liquidator, and the price at the time.
- native_prices_dailyTo buildOracle prices by dayReference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time.
- Hyperliquid core clearinghouse positions with liquidation prices for BTC and ETH perps
- Aave v3 Supply, Borrow, Repay and Withdraw events to enumerate borrowers, then getUserAccountData() and per-reserve liquidation thresholds at the snapshot block
- Morpho Blue market positions and LLTV per market
- Compound v3 user collateral and borrow balances with liquidateCollateralFactor
- The Chainlink price aggregators each protocol uses, read at the snapshot block
Questions
Questions people ask.
What is a liquidation heatmap?
A chart of the prices at which open leveraged positions would be liquidated, shaded by how much collateral would be closed at each price. Bright bands mark clusters where many positions share a level.
How are liquidation levels calculated for lending positions?
A lending position can be liquidated when its health factor falls below one. Solving for the price at which risk-adjusted collateral equals debt gives the liquidation price for that position, using the market's own threshold and oracle.
Does the heatmap include centralized exchange positions?
No. Centralized exchanges do not publish their traders' positions, so they cannot be read. The heatmap covers on-chain venues only, where every position is public state.
Why do liquidation levels move?
Borrowers repay debt, add collateral and open or close positions, and funding and interest change balances over time. Each of those changes a position's liquidation price, so the heatmap is a snapshot of one block.
Do liquidation clusters show where price will go?
No. A cluster shows where forced closing would happen if price reached it. Whether price gets there depends on the rest of the market, and positions can be adjusted before it does.
- Liquidation price
- The price at which a leveraged position falls below its maintenance requirement and can be closed by force.
- LLTV
- Liquidation loan-to-value: on Morpho Blue, the debt-to-collateral ratio above which a position can be liquidated.
- Liquidation threshold
- On Aave, the share of a collateral's value that counts toward a borrower's health; it sets where liquidation starts.
Related
More apps like this.
ETH Liquidation Levels on DeFi Lending Markets
How much ETH and BTC collateral on Aave, Spark, Compound and Morpho would become liquidatable at each price below the current one.
Multi-chainEthereumBase+1Crypto Liquidations Today: Longs vs Shorts
Leveraged positions force-closed in the last 24 hours, longs against shorts, by coin and venue, with exchange-reported totals kept apart.
Multi-chainHyperliquidEthereum+2DeFi Liquidations Tracker: Lending and Perp DEXs
Every on-chain liquidation on lending markets and perp DEXs: collateral seized, debt repaid, the liquidator and the price at the block.
Multi-chainEthereumBase+2Hyperliquid Whale Tracker: Largest Open Positions
The largest open perpetual positions on Hyperliquid by address: size, side, leverage, entry, liquidation price and unrealized profit.
HyperliquidAave Rates: Borrow and Supply APY by Market
Supply APY, variable borrow APY and utilization for every asset on every Aave market, read from each reserve's on-chain data.
Multi-chainEthereumArbitrum+3Crypto Market Cap Rankings with On-Chain Supply
The largest cryptocurrencies ranked by market cap, with each coin's supply read from its chain and the source of its price named.
Multi-chainBitcoinEthereumBuild Liquidation Heatmap from On-Chain Positions on verified data.
Start 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.