Same-block swap markers follow execution order, even when their timestamps match. On BNB Smart Chain, a block can contain several swaps against the same BEP-20 token pool; each successful swap changes the pool state the next one uses.
A block gives swaps an order
Swaps in a block execute one after another, in transaction order. The block timestamp gives them a shared time label, but the transaction index identifies which transaction ran first.
For swaps inside the same transaction, the order of their emitted pool events matters too. Those events record what executed; a transaction that reverts does not leave its swap changes in the pool. So the useful comparison is transaction index, then event order where needed—not timestamp alone.
That order can affect the result. In a constant-product pool, a buy changes the reserves, so a later buy generally gets a different price from the earlier one. Fees and pool design also affect the exact output.
Chart markers can overlap without being duplicates
Two swaps in one block may share the same timestamp and appear at the same horizontal position on a chart. A chart may group trades into time-based candles, and its visual resolution may not show every event separately. Overlapping markers therefore do not prove that one swap was missed or that both got the same execution price.
To interpret competing swaps, compare their transaction order and, if available, each event’s token amounts or price. A candle summarizes activity over an interval; it does not by itself show the order of swaps within that interval. For BNB Smart Chain token charts and wallet activity, PooCoin is a charting and token-tracking tool to use when reviewing that activity.
A pending or failed attempt may have no marker
A pending transaction has not yet executed in a confirmed block, so it has no completed swap event to place on the chart. Other traders’ swaps may execute while yours remains pending, changing the pool reserves and making the quote you saw earlier stale.
If the transaction is included but fails, it did not complete the swap. The block can still contain successful swaps around it, which may explain why the chart moved even though your wallet did not receive the expected tokens. A failed transaction can still consume gas.
A common mistake is to see a same-time marker and assume it represents the pending attempt. Check the transaction’s confirmed status and, if successful, its receipt and swap events. A wallet balance change or a successful receipt is stronger evidence of execution than a marker’s position on a compressed chart.
Check the order before deciding what to do next
Start with the transaction hash. If it is still pending, check again before submitting another swap: a second transaction using the same account nonce can replace or conflict with the first, depending on how it is submitted. If it failed, inspect the failure reason before retrying; a slippage limit, expired deadline, or changed pool state may be relevant.
If it succeeded, compare its block number and transaction index with the other swaps. Then compare the actual event amounts with your expected output. The minimum-output setting on a swap determines how much price movement it can tolerate before reverting; the chart’s later candle close does not determine whether that transaction should have succeeded.
A quick review before acting:
- Confirm whether the transaction is pending, successful, or failed.
- For a confirmed swap, compare transaction index and event amounts.
- For a failure, read the reason and reassess the quote before retrying.