How to Read and Understand Your Full Trade History on an Exchange?

Accessing Your Trade History Interface

1. Log in to your exchange account using verified credentials and two-factor authentication to ensure secure entry.

2. Navigate to the account dashboard and locate the “Trade History”, “Order History”, or “Fills” section—exact labeling varies across platforms like Binance, Bybit, or OKX.
3. Select the appropriate time range filter; some exchanges default to 24 hours while others allow custom date selection spanning months.
4. Confirm whether the view displays executed trades only or includes pending, canceled, and rejected orders—this distinction affects data interpretation.
5. Check if the interface supports CSV export functionality, which enables offline analysis using spreadsheet tools or Python-based parsing scripts.

Decoding Core Trade Record Fields

1. Order ID is a unique alphanumeric string assigned per execution, essential for dispute resolution and API reconciliation.

2. Symbol indicates the trading pair—e.g., BTC/USDT—where base and quote assets define price denomination and settlement logic.
3. Side specifies whether the trade was a buy or sell, directly influencing position direction and funding calculations in perpetual contracts.
4. Price reflects the actual fill price, not the order’s limit or market trigger level—critical when assessing slippage against entry expectations.
5. Quantity shows the executed size in the base asset, while Quote Quantity reveals the corresponding value in the counter currency, enabling PnL validation.

Recognizing Execution Types and Their Implications

1. Maker trades add liquidity by resting on the order book and receive fee rebates on most exchanges, visible as negative fee values in records.

2. Taker trades remove liquidity by matching immediately against existing orders and incur standard taker fees, often higher than maker rates.
3. Liquidation entries appear with distinct markers—such as “LIQ” or “AUTO-DELEVERAGE”—and carry zero user-initiated order IDs, signaling forced position closure.
4. Stop Market and Stop Limit fills may show delayed timestamps relative to trigger conditions, revealing gaps between activation and execution.
5. Cross-Margin versus Isolated Margin labels determine which wallet balance absorbed losses or gains, impacting equity tracking across multiple positions.

Verifying Consistency Across Data Sources

1. Compare trade timestamps between exchange UI, email confirmations, and WebSocket feed logs—millisecond-level discrepancies may indicate latency or clock drift.

2. Reconcile cumulative base asset balances before and after each trade using deposit/withdrawal records and known fee deductions to detect unlogged adjustments.
3. Cross-check average fill prices for multi-leg orders against weighted averages derived from individual fills listed in the history table.
4. Validate that all margin trades reflect correct leverage multipliers and initial margin deductions reflected in the “Margin Balance” log entries.
5. Identify duplicate entries caused by retry logic during network instability—these often share identical timestamps, prices, and quantities but differ in Order ID suffixes.

Frequently Asked Questions

Q: Why does my trade history show a different price than the chart candle at the same timestamp?A: Chart candles aggregate all trades within a time window using open-high-low-close methodology, while trade history lists individual executions—price divergence occurs due to intra-candle volatility and partial fills.

Q: Can I retrieve trade history older than 90 days on Binance?A: Yes—Binance provides extended history via the “API Key Management” page where users can request historical data exports covering up to 12 months for verified accounts.

Q: What does “Self-Trade Prevention” mean when it appears next to a canceled order?A: It indicates the exchange automatically blocked an order that would have matched against one of the user’s own resting orders, enforcing STP rules to prevent artificial volume inflation.

Q: Why are some trades marked as “Hidden” in my Bybit history?A: Hidden trades occur when iceberg orders reveal only a portion of their total size; the remaining quantity remains off the public order book and is logged separately with reduced visibility flags.