How to tell whether a candle includes private-relay trades

You cannot tell from a candle alone whether its trades arrived through a private relay: once a swap is included in a block, its on-chain effects can be read in transaction logs. A private relay changes how a transaction reaches block builders before inclusion; it does not erase the confirmed transaction from the chain. Flashbots’ documentation describes private transactions as hidden from the public mempool before inclusion, while Uniswap’s subgraph documentation records swap events by transaction and log index.

A charting service collects swap data for a pool, assigns each trade a price and volume, then groups those trades into time intervals. For each interval, the first price is the open, the last is the close, and the highest and lowest are the high and low. This is like sorting receipts into hourly folders: the folder shows what happened during the hour, not how each receipt reached the register. A candle therefore cannot identify a transaction’s original route.

What does a private relay change?

A trader signs a transaction and sends it to a private relay or builder instead of broadcasting it to the public transaction pool. The relay passes it into block construction; a validator proposes the resulting block, and the transaction becomes publicly inspectable after inclusion. The transaction may still emit the same pool swap event as a trade sent through a public route. A chart built from those events can count either kind.

That means a candle can include privately routed swaps without showing a “private” label. For more on why token identity matters before relying on a displayed swap quote, see this fuller account of Poocoin token checks and the swap quote. The same discipline applies here: first verify the token and pool, then assess the chart’s trade data.

How can you check a trade against the candle?

Start with the chain and the exact pool. Find the transaction hash, confirm that it succeeded, and inspect its receipt for the pool’s swap event and the token amounts. On Uniswap v3, the pool emits a `Swap` event; Uniswap’s documentation describes indexed swap records with a transaction reference and log index. A block explorer can show the receipt and logs, while a node’s RPC interface can retrieve them directly.

• Confirm the chain, token contract addresses and pool address. Similar token names do not establish that a chart tracks the right market.
• Check the transaction’s status, block and timestamp. A failed transaction did not complete the swap.
• Read the pool event’s amounts and resulting price. A router transaction may touch several pools, so inspect the event for the charted pool specifically.
• Compare the event time and price with the chart’s interval, then check whether the chart’s volume is denominated in the base token or quote token.

If the event appears on-chain but the candle does not seem to reflect it, the chart may use another pool, a different time boundary, or an index that has not caught up. It may also apply its own rules for trade inclusion or price conversion. A chart display alone cannot distinguish those possibilities.

Can a chart prove which trades it includes?

Only if its data source explains how it builds candles and exposes the underlying trades. Check which pools it indexes, whether it reads confirmed on-chain swap events, how it handles multiple pools, and how it defines candle boundaries. Poocoin or any other chart interface may help locate a market, but the interface itself does not prove which event created a candle.

For a reliable check, match the candle’s market and time window to successful swap events from the pool. Treat private routing as a pre-inclusion detail: after confirmation, the event can be checked like any other. The remaining uncertainty is usually the chart’s indexing and aggregation policy, not whether private-relay trades are inherently invisible.