Detail view

CHR funding

Review CHR 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.0328%

Xt · USDT

Venue coverage

11

Active CHR snapshots

Live market snapshot

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

Highest

trending_up

+0.0328%

Peak positive

Lowest

trending_down

0.0000%

Peak negative

Mean funding

equalizer

+0.0110%

Composite

Current APY

percent

+12.06%

Extrapolated from backend data.

Funding rate comparison

CHR — multi-exchange funding history

Compare historical funding rates across multiple exchanges. Each exchange is a separate line.

Exchanges (select 1–6)

14 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 CHR 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
XtUSDT▲+0.0328%+35.92%Every 8hschedule--
BinanceUSDT▲+0.0100%+10.95%Every 8hscheduleOct 04, 16:00 UTC
BingxUSDT▲+0.0100%+10.95%Every 8hscheduleOct 04, 16:00 UTC
BitgetUSDT▲+0.0100%+10.95%Every 8hscheduleOct 04, 16:00 UTC
BtseUSD▲+0.0100%+10.95%Every 8hschedule--
BybitUSDT▲+0.0100%+10.95%Every 8hscheduleOct 04, 16:00 UTC
GateUSDT▲+0.0100%+10.95%Every 8hscheduleJan 01, 00:00 UTC
KucoinUSDT▲+0.0100%+10.95%Every 8hscheduleOct 04, 16:00 UTC
MexcUSDT▲+0.0100%+10.95%Every 8hscheduleOct 04, 16:00 UTC
BlofinUSDT▲+0.0083%+9.12%Every 8hscheduleOct 01, 00:00 UTC
BitunixUSDT▲0.0000%0.00%Every 8hscheduleOct 04, 16:00 UTC

Venue breakdown

0 funding records found for CHR.

Open monitor
finance

No funding records for CHR yet.

The backend snapshot may still be refreshing.