Detail view

LSK funding

Review LSK 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.3691%

Phemex · USDT

Venue coverage

11

Active LSK snapshots

Live market snapshot

LSK funding is negative at +0.1008%, but the +0.3741% spread across 11 exchanges is wide: some venues are much cheaper to short than others, which creates cross-exchange funding opportunities.

Highest

trending_up

+0.0050%

Peak positive

Lowest

trending_down

-0.3691%

Peak negative

Mean funding

equalizer

-0.0999%

Composite

Current APY

percent

-188.25%

Extrapolated from backend data.

Funding rate comparison

LSK — 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 LSK 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.0050%+5.52%Every 8hschedule--
BitunixUSDT▲0.0000%0.00%Every 8hscheduleSep 18, 15:00 UTC
MexcUSDT▼-0.0425%-46.54%Every 8hschedule--
BybitUSDT▼-0.0568%-62.18%Every 8hscheduleSep 18, 15:00 UTC
PionexUSDT▼-0.0801%-87.75%Every 8hscheduleSep 18, 15:00 UTC
BitgetUSDT▼-0.1024%-112.13%Every 8hschedule--
BinanceUSDT▼-0.1099%-120.29%Every 8hscheduleSep 18, 15:00 UTC
AsterUSDT▼-0.1132%-991.41%Every 1hscheduleSep 18, 15:00 UTC
GateUSDT▼-0.1132%-123.95%Every 8hscheduleJan 01, 00:00 UTC
BingxUSDT▼-0.1168%-127.90%Every 8hschedule--
PhemexUSDT▼-0.3691%-404.14%Every 8hschedule--

Venue breakdown

0 funding records found for LSK.

Open monitor
finance

No funding records for LSK yet.

The backend snapshot may still be refreshing.