Detail view

HANMI funding

Review HANMI funding rates, settlement timing, and venue-by-venue snapshots from CoinCryptoRank's first-party funding feed across 11 exchanges.

11 pairs trackedscheduleexchangesverifiedFirst-party data

Top venue rate

-0.0416%

Grvt · USDT

Venue coverage

11

Active HANMI snapshots

Live market snapshot

HANMI funding is roughly flat at +0.0140% across 11 venues — a tight +0.0416% band means no venue is paying meaningfully more, so funding arbitrage is quiet right now.

Highest

trending_up

0.0000%

Peak positive

Lowest

trending_down

-0.0416%

Peak negative

Mean funding

equalizer

-0.0140%

Composite

Current APY

percent

-17.94%

Extrapolated from backend data.

Funding rate comparison

HANMI — 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 HANMI funding rate by exchange

Live funding rate and annualized APR for {symbol} perpetual contracts on each exchange — updated continuously from exchange data.

Live data
VenueFunding rateAnnualized APRSettlement frequencyNext apply
BitunixUSDT▲0.0000%0.00%Every 8hscheduleOct 17, 00:00 UTC
BybitUSDT▲0.0000%0.00%Every 8hscheduleOct 17, 00:00 UTC
DeepcoinUSDT▲0.0000%0.00%Every 8hschedule--
GateUSDT▲0.0000%0.00%Every 8hscheduleJan 01, 00:00 UTC
KucoinUSDT▲0.0000%0.00%Every 8hscheduleOct 17, 00:00 UTC
BitgetUSDT▼-0.0105%-11.50%Every 8hscheduleOct 17, 00:00 UTC
OkxUSDT▼-0.0213%-23.32%Every 8hscheduleOct 17, 08:00 UTC
XtUSDT▼-0.0263%-28.82%Every 8hschedule--
BingxUSD▼-0.0266%-58.34%Every 4hscheduleOct 17, 00:00 UTC
BinanceUSDT▼-0.0272%-29.83%Every 8hscheduleOct 17, 00:00 UTC
GrvtUSDT▼-0.0416%-45.55%Every 8hschedule--

Venue breakdown

0 funding records found for HANMI.

Open monitor
finance

No funding records for HANMI yet.

The backend snapshot may still be refreshing.