Crypto Futures Contract Explorer: Compare Leverage at Size

Set the full position value before sorting by leverage. A maximum advertised for the smallest bracket may not apply to a larger position. The displayed leverage is derived from the bracket covering your entered value, subject to documented limits. The input represents exposure in dollars, not the amount deposited as margin.

Decide whether that value describes your total position or a single order. Those are different questions. A venue might allow a $300,000 position while limiting each order to $100,000. In total-position mode, a $200,000 scenario is not rejected solely because of that smaller order cap. In one-order mode, the same amount exceeds the documented order limit.

This distinction does not establish that two $100,000 orders will fill, or that the account can actually hold $200,000. It tells you which published limit is relevant to the comparison. Execution coverage belongs in the slippage tool, and any account-specific limit remains separate from this public index.

At $1 million, the captured KuCoin XBTUSDTM tier publishes 75× alongside a 1.4% initial-margin rate. The rate requires $14,000, limiting effective leverage to 71.43×. Bybit BTCUSDT’s captured bracket permits 100× at that exposure, requiring $10,000 of base margin. These are different collateral requirements for the same total position value, not two estimates of trading profit.

If you intend 80× at that size, the retained KuCoin schedule fails the opening-margin constraint while the Bybit schedule passes that particular test. At 50×, both pass the tier ceiling, so the next comparison should move to the actual fee channel and executable book. There is no need to award a universal winner once the relevant constraint stops distinguishing them.

These two USD-denominated tier inputs were checked against public responses on 8 October. Account eligibility, extra reserves and single-order acceptance remain separate. Pin the two exact contracts to keep the comparison visible, then choose Total position or Single order according to what you are testing.

Use the exchange, asset, venue type and collateral controls to narrow the catalogue. Search also recognizes older RNDR and MATIC naming when locating indexed RENDER and POL records. An alias helps find the current record; it is not evidence that an old contract remains open for trading.

Pin up to three contracts. The comparison keeps collateral, initial margin, maintenance margin, fee references and limits in aligned rows. It remains available when you adjust filters, so you can add a second exchange without losing the first selection. Remove a pin explicitly when that record no longer belongs in the comparison.

Collateral can change the meaning of otherwise similar products. USDT and USDC settlement are not the same balance, and a token-collateralized or inverse contract cannot be treated as a linear dollar-settled position merely because both display BTC. The explorer shows the recorded collateral; it does not convert every product into a common economic model.

Alphabetical order is deliberately neutral. You can choose leverage-at-size sorting or record-date sorting, but those controls do not rank withdrawal reliability, market depth, legal access or trading quality. The name of a sort should describe exactly what moved the cards.

A complete bracket supplies enough documented inputs to show the margin rates at the selected size. The complete-bracket filter removes rows that cannot supply those fields. It does not upgrade a public bracket into a guarantee that your account is assigned the same risk limit.

Initial margin concerns opening or supporting exposure; maintenance margin concerns the threshold used by the risk model. They should not be swapped when judging how far a position can move before liquidation. A bracket with a high leverage ceiling can still have maintenance requirements and deductions that need a separate calculation.

Maker and taker percentages are public reference inputs from their own sources. They may come from a published schedule or API metadata. They are not your authenticated fee quote, and the label does not assert that a temporary campaign applies to your account. Missing rates stay missing rather than becoming zero.

Open the field evidence when a number changes the decision. The leverage, margin brackets, caps, rates and funding interval can have different verification dates. A recently updated record can contain an older fee source. Sorting by record date does not erase that distinction or claim that every field was fetched at the same moment.

The liquidation-model link preserves the selected exchange, asset and position amount when a matching linear isolated model exists. It leaves entry price for you to supply. A contract catalogue identifies a product; it does not tell us where you entered or intend to enter.

The transferred reference taker rate becomes an explicit scenario input. Verify it against your account if you use the scenario for planning. The linked calculator also shows its own contract evidence and any more recent model input; the catalogue snapshot should not overwrite fresher documented rules silently.

Where no supported equivalent exists, the explorer links the exchange dossier without substituting another venue or a loosely related product. This is especially important for pool-based protocols, collateral variants and legacy products. Sending every selection to a generic search would make a precise-looking contract choice misleading.

Filters are reflected in the page URL, including position amount, sort and order-versus-position scope. Copy the address to share that view, and use browser Back to return through changes. Pins belong to the current session and are not represented as permanent research selections. Reset clears the comparison and returns to the default catalogue.

The displayed count is derived from the loaded index. It is not a hard-coded claim about how many futures products exist in the market. The catalogue covers selected assets and documented records, so a search that returns nothing is a coverage gap, not a delisting announcement.

If a result is unavailable at your size, distinguish an explicit cap from an absent bracket. The first supports a concrete conclusion about the recorded limit. The second says the dataset cannot calculate that scenario. Keeping those outcomes separate is more useful than placing both under a broad “unsupported” badge.

The dated field references are also the boundary of this tool’s freshness claim. Reading the page today does not recheck every exchange policy. A contract update, account migration or new fee tier should be confirmed in the relevant source before replacing a working account assumption.