Skip to content
PerpFinder

Perp Market Week 38, 2026: Volume, Funding, Costs

PerpFinder editorial · Published

In ISO week 38 of 2026, the stored daily snapshots hold $1,446.54 billion of centralized perpetual volume. The perp-DEX protocols hold $153.65 billion over the same days, a share of 9.60 percent. The open-interest-weighted BTC funding rate held a median of 0.000890 percent per hour, or 7.80 percent at a simple annual rate. A $1,000,000 BTC perpetual order cost a median of 6.348 basis points across 950 order-book observations.

Period (UTC)2026-09-14 00:00 UTC2026-09-20 23:59 UTC
Published2026-09-23
Max samples/series950
Min completeness85.7%
Facts / suppressed56 / 0

Measurements of stored PerpFinder data, never accusations. A weekly figure is the sum of stored daily snapshots and not an exact calendar week. A venue-day that the spike rule holds out stays visible in the spike table. This report does not claim that any venue misreports volume.

What this report measures

PerpFinder collects four stored series of the perpetual market. The daily snapshot series stores the reported 24-hour volume of each venue once a day. The funding sweep stores the rate of each venue every 15 minutes. The execution-cost sweep walks the order book of each venue every 6 hours. This report reads those stored series for ISO week 38 of 2026, which runs from 2026-09-14 to 2026-09-20.

Each weekly volume figure is the sum of 7 stored daily snapshots. A snapshot covers the 24 hours before its own capture instant. The sum therefore measures 7 stored days, and it does not measure an exact calendar week. Each table on this page states its own measurement instant, because the collection clocks are different.

The generator reads only stored PerpFinder data. It fetches no venue endpoint at build time, and it writes no value that the stored series does not hold. The methodology of each series is on the research hub.

Volume in week 38 against week 37

The centralized venues stored $1,446.54 billion of perpetual volume across the 7 days of 2026-W38. The perp-DEX protocols stored $153.65 billion across the same 7 days. Both figures apply the spike rule. That rule holds a venue-day above 3 times the 7-day median of the same venue out of the total.

The stored total of 2026-W37 is $1,300.02 billion. That week rests on 7 captured days. The two weeks do not store the same venue set on every day, so a comparison of the two headline totals compares two different venue sets.

The comparable set holds the 21 venues that both weeks store on every day. On that set the centralized total moved from $1,244.82 billion to $1,446.54 billion, a change of 16.2 percent. The set also leaves out BitMEX, Bitmart, because 2026-W38 does not store those venues on every day.

Stored measurements · USD billions

Daily volume by venue type

DEXCEX
212.114
249.115
238.616
263.617
271.618
180.519
184.720

Day of 2026-09 · zero baseline · totals above bars

2026-09-14 00:00 UTC to 2026-09-20 23:59 UTC — one stored snapshot per day, capture time in the second column. Each row is one stored daily snapshot. The centralized figure sums the venues of that day after the spike rule. The perp-DEX figure is the stored daily total across the protocols with a positive figure. A day that stores no perp-DEX row keeps a null cell. Source: PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history. The data table contains the plotted values.

Measured perpetual volume per stored day, 2026-W38

Measured at 2026-09-14 00:00 UTC to 2026-09-20 23:59 UTC — one stored snapshot per day, capture time in the second column · PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history

Each row is one stored daily snapshot. The centralized figure sums the venues of that day after the spike rule. The perp-DEX figure is the stored daily total across the protocols with a positive figure. A day that stores no perp-DEX row keeps a null cell. Download this table as CSV

DateCapture (UTC)CEX venuesCEX volume ($B)DEX volume ($B)DEX protocolsDEX share (%)Spike-flagged venue-days
2026-09-1418:0322197.514.62896.890
2026-09-1516:5322223.5625.499110.240
2026-09-1616:4722212.7825.838910.821
2026-09-1716:5421238.3325.24909.580
2026-09-1816:2021249.7521.88918.060
2026-09-1915:5021153.5926.929314.912
2026-09-2015:5921171.0313.68927.410

Scroll the columns sideways to see every field. The CSV holds the same rows.

The spike rule and the venue-days it held out

PerpFinder flags a venue-day when the venue reports more than 3 times the median of its own previous 7 stored days. A flagged venue stays visible on the site and leaves the headline total until the figure holds. The rule needs at least 3 stored days behind the median.

The rule flagged 3 venue-days of 2026-W38. Each one stays in the spike table and leaves the headline total. The rule flagged 1 venue-day of 2026-W37, and the spike table names each one.

A flagged venue-day is a measurement of the reported figure against the venue own recent history, and it is not a statement about the venue.

Venue-days that the spike rule held out, 2026-W38 and 2026-W37

Measured at 2026-09-14 00:00 UTC to 2026-09-20 23:59 UTC and 2026-09-07 00:00 UTC to 2026-09-13 23:59 UTC — stored daily snapshots · PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history

A venue-day enters this table when the venue reported more than 3 times the median of its own previous seven stored days. The venue-day stays visible and leaves the headline total. The baseline column counts the stored days behind the median. Download this table as CSV

VenueDateReported 24h ($M)7-day median ($M)MultipleBaseline days
Backpack2026-09-10397.6118.83.37
BitMEX2026-09-16182.28.47
WhiteBIT2026-09-1951186.36709.97.67
WEEX2026-09-1944273.912280.23.67

Scroll the columns sideways to see every field. The CSV holds the same rows.

Venue ranks and the moves inside them

The comparable set puts five venues at the top of 2026-W38. The list is Binance at $419.20 billion, OKX at $169.60 billion, Toobit at $125.93 billion, WEEX at $101.98 billion, Bybit at $101.16 billion.

The rank table counts the venue-days that entered each weekly figure. The spike rule took 3 venue-days out of 2026-W38 and 1 venue-day out of 2026-W37, so a venue with a lower day count also carries a lower weekly figure. A move that pairs with a different day count is partly a coverage effect.

Among the venues with 7 counted days in both weeks, the largest move belongs to XT.COM, from rank 10 to rank 8.

Venue rank and weekly volume, 2026-W38 against 2026-W37

Measured at 2026-09-14 00:00 UTC to 2026-09-20 23:59 UTC and 2026-09-07 00:00 UTC to 2026-09-13 23:59 UTC · PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history

The table holds the venues that both weeks store on every day. The days column counts the venue-days that entered each weekly figure, so a venue that lost a day to the spike rule shows a lower count and a lower figure. A rank move with different day counts is partly a coverage effect. Download this table as CSV

VenueRank 2026-W38Rank 2026-W37Move2026-W38 ($B)2026-W37 ($B)Days 2026-W38Days 2026-W37
Binance110419.2361.4777
OKX220169.6145.177
Toobit330125.93123.9677
WEEX47+3101.9860.1767
Bybit54-1101.1685.0577
Gate.io65-199.9181.5177
MEXC76-178.9976.7777
XT.COM810+254.8746.8577
Bitget99054.4747.7977
Coinbase1011+154.0144.3877
WhiteBIT118-346.7449.2767
BingX1212044.9242.1477
Bitunix1313042.3836.8377
KuCoin1414014.9911.8877
HTX151509.769.3377
Kraken161607.355.7277
BloFin171705.494.5277
Phemex181805.154.2577
Deribit1920+14.543.2277
Crypto.com2019-13.623.3377
Backpack212101.471.2876

Scroll the columns sideways to see every field. The CSV holds the same rows.

Perp-DEX share of the measured volume

The perp-DEX protocols hold 9.60 percent of the measured perpetual volume of 2026-W38. The share divides the stored perp-DEX total by the sum of that total and the centralized total.

The daily share moved between 6.89 percent on 2026-09-14 and 14.91 percent on 2026-09-19. Both ends come from the daily volume table.

The share of 2026-W37 is 9.06 percent.

BTC funding: level and cross-venue spread

The open-interest-weighted BTC funding rate held a median of 0.000890 percent per hour across the 672 sweeps of 2026-W38. At a simple annual rate that median is 7.80 percent. The median stayed positive, so a long paid the short over the week on the weighted average of the venues.

The cross-venue spread is the highest venue rate minus the lowest venue rate in one sweep. Its median over the week is 0.00254 percentage points per hour. The widest single sweep of the week is 2026-09-18 16:00 UTC, at 0.00738 percentage points per hour. In that sweep 24 venues published a rate, between -0.00516 percent and 0.00222 percent per hour.

The week stored 672 of the 672 sweeps that a full week holds at this cadence. Venue coverage stayed between 24 and 27 venues per sweep.

BTC funding level and cross-venue spread per day, 2026-W38

Measured at 2026-09-14 00:00 UTC to 2026-09-20 23:59 UTC — 672 sweeps at a 15-minute cadence · PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates

The open-interest-weighted rate weights each venue by its own open interest in the same sweep. The spread is the highest venue rate minus the lowest venue rate in one sweep. All figures are percent per hour. Download this table as CSV

DateSweepsOI-weighted median (%/h)Median spread (pp/h)Widest spread (pp/h)
2026-09-14960.0007650.002580.00404
2026-09-15960.0006710.002280.00403
2026-09-16960.0008920.002310.00362
2026-09-17960.0009050.002540.00383
2026-09-18960.0008750.003070.00738
2026-09-19960.0010820.002640.00378
2026-09-20960.0010660.002190.00378

Realized funding, venue by venue

The realized ledger stores each settlement that a venue published. For 2026-W38 it holds 420 settlements from 6 venues, and every one of those venues published a complete week.

A long position paid the most on Hyperliquid, at 0.1978 percent of the position over the week. A long paid the least on dYdX, at 0.0330 percent of the position over the week. A negative figure means a long received funding instead of paying it.

The settlement interval differs between venues, so the realized table states the interval of each venue in minutes. A venue with a shorter interval writes more rows into the ledger. The weekly sum stays comparable between venues, because each sum covers the same period.

Stored settlements · percent over the week

Funding paid or received by a long

Received (−)Paid (+)
Hyperliquid+0.1978%
Binance+0.1488%
OKX+0.1444%
Bybit+0.1233%
Gate.io+0.1177%
dYdX+0.0330%

Positive means the long paid funding. Negative means the long received it. These observations do not predict future payments.

2026-09-14 00:00 UTC to 2026-09-20 23:59 UTC — 420 stored settlements. The value is the sum of the settlement rates that the venue published inside the week. A positive figure means a long paid. The ledger covers the venues that publish a settlement history, so it does not describe the whole market. Source: PerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized. The data table contains the plotted values.

Realized BTC funding paid by a long, 2026-W38

Measured at 2026-09-14 00:00 UTC to 2026-09-20 23:59 UTC — 420 stored settlements · PerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized

The value is the sum of the settlement rates that the venue published inside the week. A positive figure means a long paid. The ledger covers the venues that publish a settlement history, so it does not describe the whole market. Download this table as CSV

VenuePaid over the week (%)SettlementsExpectedInterval (min)
Hyperliquid0.197816816860
Binance0.14882121480
OKX0.14442121480
Bybit0.12332121480
Gate.io0.11772121480
dYdX0.03316816860

Execution cost of a $1,000,000 BTC perpetual order

The cost engine walks the order book of each venue every 6 hours and records the total cost of a $1,000,000 BTC perpetual order. Total cost is the taker fee plus the half-spread plus the size-dependent impact beyond the best quote. Across the 28 stored sweeps of 2026-W38 the median of the 950 order-book observations is 6.348 basis points.

The set of 31 order-book venues filled the order in every stored sweep of the week. The three lowest weekly medians in that set are Lighter at 1.238 basis points, MEXC at 2.056 basis points, Extended at 2.888 basis points. Each figure is the median of the sweeps of that venue. The cost table states the lowest sweep and the highest sweep of each venue.

An oracle venue has no order book, so it is not in these numbers. The walk found 9 venues that could not fill the order in at least one sweep, and a sweep without a fill contributes no cost figure. The week uses cost methodology version 8, which is the version the store held for the whole week.

Stored measurements · basis points

Median execution cost and observed range

Lowest to highestMedian
Lighter1.24
MEXC2.06
Extended2.89
Coinbase4.40
NADO4.51
edgeX4.72
Hyperliquid4.90
Aster4.95

Common scale: 0–6.51 bps · displayed value is the median

First 8 rows in the published table order; 35 venues in the full table. 2026-09-14 00:56 UTC to 2026-09-20 18:56 UTC — 28 sweeps, cost methodology version 8. Total cost is the taker fee plus the half-spread plus the size-dependent impact beyond the best quote. Order-book venues only; an oracle venue has no book and does not appear. The sweeps column counts the sweeps in which the venue filled the order. Source: PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history. The data table contains the plotted values.

Total execution cost of a $1,000,000 BTC perpetual order, 2026-W38

Measured at 2026-09-14 00:56 UTC to 2026-09-20 18:56 UTC — 28 sweeps, cost methodology version 8 · PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history

Total cost is the taker fee plus the half-spread plus the size-dependent impact beyond the best quote. Order-book venues only; an oracle venue has no book and does not appear. The sweeps column counts the sweeps in which the venue filled the order. Download this table as CSV

VenueTypeMedian total (bps)Lowest (bps)Highest (bps)Sweeps
Lighterdex1.2380.9672.62428
MEXCcex2.0562.0063.03728
Extendeddex2.8882.5625.46528
Coinbasecex4.3984.0615.73628
NADOdex4.5084.0486.51528
edgeXdex4.7244.5615.50128
Hyperliquiddex4.8964.5616.2528
Asterdex4.9534.5076.09928
GRVTdex5.1134.6931.77227
Binancecex5.1775.0066.27528
OKXcex5.3015.0066.54628
BingXcex5.4515.0266.15728
Toobitcex6.0066.0066.55628
Bitunixcex6.0446.0296.06528
XT.COMcex6.0796.0186.49428
Bybitcex6.1215.5067.53528
Gate.iocex6.3465.3567.66128
BloFincex6.396.0139.06228
HTXcex6.4546.0798.80128
Bitgetcex6.6666.0287.98328
Deribitcex7.3144.49910.85628
Krakencex7.3836.738.47928
SunXdex7.6526.44738.30928
Phemexcex7.9796.5249.99128
KuCoincex8.067.0429.51428
WEEXcex8.0918.0368.26628
StandXdex8.1447.3538.92628
Apex Omnidex8.6115.96416.38928
Crypto.comcex9.0597.59413.24628
RISExdex11.3239.03324.28228
Aevodex12.5310.36619.7527
WhiteBITcex12.55110.76515.11728
dYdXdex15.34610.70251.80628
Ondodex23.15719.41125.2083
Hibachidex37.88826.09279.44225

Scroll the columns sideways to see every field. The CSV holds the same rows.

What this week rests on

The volume figures rest on 7 stored days, 21 centralized venues on every day and between 89 and 93 perp-DEX protocols with a positive figure. The funding figures rest on 672 sweeps and 420 stored settlements. The execution-cost figures rest on 28 sweeps and 950 order-book observations. The volume-quality series adds 28 sweeps of 20 venues inside the same week.

The week carries the gaps named here.

The comparable venue set leaves out BitMEX, Bitmart, because 2026-W38 does not store those venues on every day.

The spike rule held 1 venue-day out of the 2026-W37 total.

The cost series carries fewer than 28 sweeps for 4 order-book venues, so the weekly median of those venues rests on a shorter series.

Methodology versions inside 2026-W38

Measured at 2026-09-14 00:00 UTC to 2026-09-20 23:59 UTC — stored points of each version · PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates; PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history; PerpFinder volume-quality sweeps — /api/data/volume-quality-history

Each versioned series stores every methodology version apart. The report uses the version with the most points inside the week and never merges two versions. The points column counts the stored points of each version inside the week. Download this table as CSV

SeriesVersionPoints in the weekUsed in this report
BTC funding sweeps2672yes
Execution-cost sweeps828yes
Volume-quality sweeps328yes

Limitations

Reported volume comes from the ticker endpoint of each venue. PerpFinder normalizes the unit and the market type, and does not audit the venue figure.

A daily snapshot is one reading per day. A venue that moved inside the day, or that published a different figure at another hour, produces a different weekly sum on another clock.

The funding sweep and the cost sweep each read one instant. Depth and rates change between readings, and a later reading returns different numbers.

The realized ledger covers the venues that publish a settlement history. It does not describe the venues that publish none.

How to reproduce these numbers

Every number comes from public endpoints that need no key. The funding figures come from https://perpfinder.com/api/data/funding-history?asset=BTC&type=aggregates&days=30 and from the same endpoint with type=realized. The execution-cost figures come from https://perpfinder.com/api/data/cost-history?market=perp&asset=BTC&size=1000000&days=all. The volume figures come from https://perpfinder.com/api/data/venue-history?venue=Binance&days=30 and the same endpoint for each venue.

Those endpoints serve the current state, so a later call returns later numbers. Each table on this page carries a CSV with the exact rows of 2026-W38, and the fact block carries a CSV of every headline figure.

Collection cadence and updates

The collection cadence is fixed. The funding sweep runs every 15 minutes, the execution-cost sweep and the volume-quality sweep run every 6 hours, and the venue snapshot runs each day.

PerpFinder keeps no fixed publication schedule for this series. A published report is not edited after publication, and a later week is published as a new page.

The numbers

MetricValue
Centralized perpetual volume, 2026-W38 (USD billion, sum of 7 stored daily snapshots, spike rule applied)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history1,446.54
Centralized perpetual volume, 2026-W37 (USD billion, sum of 7 stored daily snapshots, spike rule applied)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history1,300.02
Centralized perpetual volume, 2026-W38, venues stored on every day of both weeks (USD billion)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history1,446.54
Centralized perpetual volume, 2026-W37, venues stored on every day of both weeks (USD billion)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history1,244.82
Week-over-week change of centralized perpetual volume on the comparable venue set (percent)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history16.2
Centralized venues with a stored 24-hour figure on every day of 2026-W38PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history21
Perp-DEX volume, 2026-W38 (USD billion, sum of 7 stored daily snapshots)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history153.65
Days of 2026-W37 that store a perp-DEX totalPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history7
Perp-DEX share of measured perpetual volume, 2026-W38 (percent)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history9.6
Perp-DEX share of measured perpetual volume, 2026-W37 (percent)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history9.06
Stored daily snapshots inside 2026-W38PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history7
Window that one stored daily snapshot covers, counted back from its own capture instant (hours)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history24
Centralized venues that both 2026-W38 and 2026-W37 store on every dayPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history21
Fewest perp-DEX protocols with a positive figure on one day of 2026-W38PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history89
Most perp-DEX protocols with a positive figure on one day of 2026-W38PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history93
Spike rule: a venue-day above this multiple of the venue own 7-day median leaves the headline totalPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history3
Stored days that the spike-rule median looks back overPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history7
Stored days the spike rule needs behind a median before it judges a venue-dayPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history3
Venue-days of 2026-W38 that the spike rule held out of the headline totalPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history3
Venue-days of 2026-W37 that the spike rule held out of the headline totalPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history1
Days of 2026-W37 that were reconstructed after the fact instead of capturedPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history0
Binance perpetual volume, 2026-W38 (USD billion, rank 1 of the comparable venue set)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history419.2
OKX perpetual volume, 2026-W38 (USD billion, rank 2 of the comparable venue set)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history169.6
Toobit perpetual volume, 2026-W38 (USD billion, rank 3 of the comparable venue set)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history125.93
WEEX perpetual volume, 2026-W38 (USD billion, rank 4 of the comparable venue set)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history101.98
Bybit perpetual volume, 2026-W38 (USD billion, rank 5 of the comparable venue set)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history101.16
BTC open-interest-weighted funding rate, median of 672 sweeps (percent per hour)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates0.0009
BTC open-interest-weighted funding rate, weekly median at an annual rate (percent, simple, 24 hours by 365 days)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates7.8
BTC cross-venue funding spread, median of the sweeps (percentage points per hour, highest venue minus lowest venue)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates0.0025
BTC cross-venue funding spread, widest single sweep of the week (2026-09-18 16:00 UTC, percentage points per hour)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates0.0074
Lowest venue funding rate in the widest sweep (2026-09-18 16:00 UTC, percent per hour)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates-0.0052
Highest venue funding rate in the widest sweep (2026-09-18 16:00 UTC, percent per hour)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates0.0022
Venues that published a BTC rate in the widest sweep (2026-09-18 16:00 UTC)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates24
Stored BTC funding sweeps inside 2026-W38PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates672
Cadence of the funding sweep (minutes)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates15
Fewest venues with a BTC rate in one sweep of 2026-W38PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates24
Most venues with a BTC rate in one sweep of 2026-W38PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates27
Sweeps a full week holds at the 15-minute cadencePerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates672
Realized BTC funding paid by a long over 2026-W38, highest venue (Hyperliquid, percent of position)PerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized0.1978
Realized BTC funding paid by a long over 2026-W38, lowest venue (dYdX, percent of position)PerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized0.033
Stored BTC funding settlements inside 2026-W38, all venues in the ledgerPerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized420
Venues that published a complete week of BTC settlements to the ledgerPerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized6
Order size of the execution-cost measurement, BTC perpetual (USD)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history1,000,000
Total execution cost of a $1,000,000 BTC perpetual order, median of every order-book observation in 2026-W38 (basis points)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history6.348
Order-book cost observations inside 2026-W38PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history950
Stored execution-cost sweeps inside 2026-W38PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history28
Cadence of the execution-cost sweep (hours)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history6
Order-book venues with a cost figure in every stored sweep of 2026-W38PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history31
Order-book venues with a cost figure in some but not every stored sweep of 2026-W38PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history4
Venues that could not fill the $1,000,000 order in at least one stored sweep of 2026-W38PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history9
Cost methodology version that the store treats as active at the time of the reportPerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history8
Lighter total execution cost of a $1,000,000 BTC perpetual order, weekly median (basis points, rank 1)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history1.238
MEXC total execution cost of a $1,000,000 BTC perpetual order, weekly median (basis points, rank 2)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history2.056
Extended total execution cost of a $1,000,000 BTC perpetual order, weekly median (basis points, rank 3)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history2.888
Stored volume-quality sweeps inside 2026-W38PerpFinder volume-quality sweeps — /api/data/volume-quality-history28
Venues in each stored volume-quality sweep of 2026-W38PerpFinder volume-quality sweeps — /api/data/volume-quality-history20

Author: PerpFinder editorial — the PerpFinder data desk. Published research carries the desk byline. Send a correction through the corrections page.

Sources: PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history · PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates · PerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized · PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history · PerpFinder volume-quality sweeps — /api/data/volume-quality-history

Facts are generated deterministically from PerpFinder’s self-collected datasets (frozen methodology, versioned for each reported series) and are never edited by hand — only the narrative around them is editorial. Republishing the numbers is welcome with attribution: data license.