PerpStart with the contract, then read the number
A rate makes sense only with the contract it belongs to. PerpFox follows BTC, ETH and SOL USDT-settled linear perpetuals. An exchange name and a ticker are part of the record, not decoration: BTCUSDT on Binance and BTC-USDT-SWAP on OKX are separate instruments. A BTC spot quote is a different market again.
The workbench places Binance first to match this site's focus. That position is not a lowest-cost recommendation. Within a row, read the current estimate, the latest actual settlement and the next settlement time separately. An empty field means we do not have that information; it never means a zero payment.
Why a Binance rate can be fresh while its timer is blank
Our Binance BTC, ETH and SOL observations come from Coinalyze's predicted-funding-rate service. The provider supplies a prediction and an update time. The current integration does not establish the contract's funding interval, next settlement time or actual settlement history.
We keep the prediction visible with its source and age. We do not infer an eight-hour interval, turn the update time into a settlement deadline or add the prediction to the historical chart. The missing schedule also keeps this record out of interval conversion, holding-period calculations and page alerts. Adding it to a watchlist remains available.
This distinction follows the fields documented by Coinalyze, checked on September 10, 2026. A provider's ability to return a number does not establish exchange access or account eligibility.
Three times that answer three different questions
| Time | What it tells you | What it does not prove |
|---|---|---|
| Source update | When the provider says its observation changed or was updated | That a payment happened |
| Fetched by PerpFox | When our collector successfully received the record | That the source observation was new |
| Settlement time | Which scheduled or actual event the rate belongs to | That your account held a position at that event |
The English workbench initially uses UTC. The time selector changes the display, not the underlying event. CSV timestamps remain in UTC, and calculator start and end fields are explicitly UTC. This helps when a screenshot, a browser and an account statement show different calendar dates.
What pauses when a source stops updating
Funding collection is scheduled about once a minute. A record older than 180 seconds is marked stale; after 300 seconds it leaves current comparisons. A reported source error also removes the qualifications needed for calculations and alerts. Refreshing the page or reading a cached response does not reset the last successful fetch.
Spot prices have a separate policy: collection about every 30 seconds, stale after 90 seconds and expired after 180 seconds. A source failure or stale timestamp removes the heat colour and valid spread calculation. The spot feed and funding feed can therefore have different states at the same moment.
These are PerpFox's operating thresholds, not a guarantee that every upstream observation is timely. If timing matters to your decision, inspect the row details and the exchange's current contract information.
A historical row is an event, not a line drawn backwards
The 7-day and 30-day choices request windows of actual settlement records. Existing OKX history uses its actual-settlement field. The current Binance provider does not populate this event history. We never fill an empty history with today's prediction.
The chart, table and history CSV use the same records. A count tells you how many events we obtained. It does not certify a complete window. Check the first and last event, backfill status, long gaps and recorded source revisions before treating a subtotal as the whole period. Chart segments stop across unusually long intervals rather than inventing intermediate points.
The calculator fixes the notional value you enter
The calculation uses funding cash flow = minus position direction times USDT notional value times the settled rate. Long is +1 and short is -1. Positive output means money received; negative output means money paid. Rates are stored as decimals: 0.0002 is 0.02%.
For a hypothetical 6,000 USDT long at a single +0.02% settlement, funding cash flow is -1.20 USDT. The same fixed notional short receives +1.20 USDT in this example. These are arithmetic examples, not current prices or an offer of returns. Binance describes position value and funding payments in its funding explanation.
Historical mode selects obtained events after the start and at or before the end: (start, end]. Future mode uses the verified next event and then assumes an unchanged rate and interval. Only that first schedule comes from a source; later events are hypothetical. The calculator does not extend a position into the past using a prediction.
Opening fees, closing fees and slippage are your inputs. They are not read from your account and no referral percentage is prefilled. Notional already includes the position exposure you chose, so the calculator does not multiply it by leverage again. Price profit or loss, basis, borrowing and liquidation are outside the displayed fee total.
Keep enough information to reproduce the result
Record the contract, direction, notional, time window, rate basis and any fee assumptions. Export the actual events when using historical mode. If a payment differs from an account statement, work through the rate-to-payment reconciliation guide; a current prediction is not evidence that the account statement is wrong.
For a source or calculation issue, use the corrections page. A contract ID, a UTC timestamp and the public field in question are usually more useful than a screenshot of an entire account.