# Batch Execution In traditional exchanges or newer AMM DEXs, prioritization of orders by sub-second latency creates huge problems around fairness of the marketplace. Especially in decentralized setup, MEV(Miner Extractable Value) is a huge cost to every ordinary traders in DEXs. In Crescent DEX, we minimize such value extraction by adopting batch execution for orderbook order matching mechanism. In batch execution, orders within a batch are treated equally without prioritization by order time. The only prioritization is the order price, not the order time. It brings healthy competition among arbitrageurs and traders which result in more efficient price discovery of the orderbook. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.crescent.network/introduction/crescent-dex-legacy/batch-execution.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.