One Click, Several Events in a Row · Tanzania
Pressing the button starts a sequence rather than completing one. What happens between the press and the confirmation, and why the gap is a stage and not a fault.
Open Exness Account →An order is not an instant. Pressing the button hands an instruction to the platform, which sends it; the server receives it, executes it against the market and returns a confirmation. Each of those is a separate event with its own place in time, and the sequence carries on after the finger has left the button. A gap between the press and the confirmation is the sequence running, not the platform hanging.
Why this is measured with trades
Execution quality is one of the account features Exness highlights, and it cannot be judged from quotes alone — only a real order shows the latency, the fill price and whether the platform rejects size. The probe opens and immediately closes positions of increasing size and records what actually happened.
Execution speed and fill quality vary with market conditions, liquidity and position size.
Measured round-trips by instrument and size
| Instrument | Lot size | Avg execution | Slowest fill | Avg slippage (signed) | Better / zero / worse fills | Rejects |
|---|---|---|---|---|---|---|
| EUR/USD | 0.01 | 151 ms | 187 ms | -0.3 pts | 1 / 2 / 0 | 0 |
| EUR/USD | 0.1 | 151 ms | 172 ms | -0.3 pts | 1 / 2 / 0 | 0 |
| EUR/USD | 1 | 146 ms | 172 ms | -0.3 pts | 1 / 2 / 0 | 0 |
| GBP/USD | 0.01 | 141 ms | 156 ms | +0.7 pts | 0 / 1 / 2 | 0 |
| GBP/USD | 0.1 | 130 ms | 140 ms | +0.0 pts | 0 / 3 / 0 | 0 |
| GBP/USD | 1 | 135 ms | 156 ms | +0.3 pts | 0 / 2 / 1 | 0 |
| XAU/USD (Gold) | 0.01 | 141 ms | 172 ms | +0.0 pts | 0 / 3 / 0 | 0 |
| XAU/USD (Gold) | 0.1 | 151 ms | 172 ms | +80.0 pts | 1 / 1 / 1 | 0 |
| XAU/USD (Gold) | 1 | 130 ms | 141 ms | -72.3 pts | 2 / 1 / 0 | 0 |
Across 27 measured round-trips the average fill took 130–151 ms depending on instrument and size, with 0 rejected orders in total. Negative slippage means the fill was better than the quoted price at the moment the order was sent.
Slippage in points, signed: negative = filled better than quoted, positive = worse. ‘Rejects’ counts orders the platform refused at that size.
How this was measured
- Real market orders (buy, then immediate close) placed in an Exness MetaTrader 5 terminal.
- Latency timed in-terminal from order send to broker confirmation.
- Sizes stepped 0.01 → 1.00 lot to expose size-dependent slippage.
- Fills depend on market liquidity, account and conditions, and can differ.
Measured in-terminal on Exness’s own MetaTrader 5 pricing feed and symbol specifications, refreshed on a schedule. All figures are indicative and change with market conditions.
Open Exness Account →Four events wearing one name
The word order is used for all four stages at once, which is where most of the confusion starts. There is the moment the platform accepts what was typed, the moment it leaves the device, the moment the server acts on it and the moment a confirmation comes back.
Only the first of those happens where the finger is. The other three happen elsewhere and continue whether or not the screen is still being watched, which is why letting go of the button is not a decision point in the process.
The confirmation reports, it does not create
A position comes into existence when the order is executed, not when the message about it appears. The confirmation is a report travelling back, and like anything travelling back it arrives after the thing it describes has already happened.
So the account history, rather than the screen, is the thing that settles whether an order exists. The screen is a good approximation and it is usually fast; it is still a copy of something written somewhere else.
Pressing again starts a second sequence
A second press does not resend the first instruction, retry it or replace it. It begins a new sequence from the first stage, and the earlier one is still somewhere in its own progression, unaware that a successor exists.
That is the practical reason a quiet moment is worth sitting through. Two presses can produce two positions, because nothing about the second one cancels the first, and both will be reported in the record.
What happens between the press and the confirmation
- The platform accepts the instruction and stops treating it as something that can still be edited.
- The instruction leaves the device and is on its way to the server.
- The server receives it, and at that point it stops being an intention and becomes an order.
- The order is executed against the market at what is available at that moment.
- A confirmation travels back and the position appears in the account record.
Only the first stage happens on the device. The account record is written at the fourth, before anything is displayed.