Top venue rate
-0.1376%
Bitunix · USDT
Detail view
UNH funding
Review UNH funding rates, settlement timing, and venue-by-venue snapshots from CoinCryptoRank's first-party funding feed across 9 exchanges.
9 pairs trackedscheduleexchangesverifiedFirst-party data
Venue coverage
9
Active UNH snapshots
Live market snapshot
UNH funding is near zero on average (+0.0165%), but the +0.1452% spread across 9 exchanges is wide — some venues still pay enough to justify selective funding arbitrage.
Highest
trending_up+0.0076%
Peak positive
Lowest
trending_down-0.1376%
Peak negative
Mean funding
equalizer-0.0145%
Composite
Current APY
percent-15.92%
Extrapolated from backend data.
Funding rate comparison
UNH — multi-exchange funding history
Compare historical funding rates across multiple exchanges. Each exchange is a separate line.
Exchanges (select 1–6)
13 exchanges available
Stats summary
Exchanges tracked
2
Data points
0
Best spread
--
Status
Ready
Fetching funding data...
Select exchanges above to compare funding rate history.
Funding rate by venue
Current UNH funding rate by exchange
Live funding rate and annualized APR for {symbol} perpetual contracts on each exchange — updated continuously from exchange data.
| Venue | Funding rate | Annualized APR | Settlement frequency | Next apply |
|---|---|---|---|---|
| BingxUSD | ▲+0.0076% | +8.32% | Every 8h | scheduleOct 17, 16:00 UTC |
| XtUSDT | ▲+0.0013% | +1.37% | Every 8h | schedule-- |
| BinanceUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleOct 17, 16:00 UTC |
| BitgetUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleOct 17, 16:00 UTC |
| BybitUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleOct 17, 16:00 UTC |
| GateUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleJan 01, 00:00 UTC |
| OkxUSDT | ▲0.0000% | 0.00% | Every 8h | scheduleOct 18, 00:00 UTC |
| BlofinUSDT | ▼-0.0021% | -2.26% | Every 8h | scheduleOct 01, 00:00 UTC |
| BitunixUSDT | ▼-0.1376% | -150.67% | Every 8h | scheduleOct 17, 16:00 UTC |
Venue breakdown
0 funding records found for UNH.
finance
No funding records for UNH yet.
The backend snapshot may still be refreshing.