BCHUSDT

Proof it was published before the outcome

No Telegram message id is recorded for this trade. That means we cannot prove pre-publication for this particular trade — and we do not hide it.

The signal's original message was posted to the channel before the outcome existed; the message id and the follow-up replies (a TP or SL hit) are stored in this same record.

Take-profit ladder

This trade's six take-profit rungs and which of them actually filled. An unfilled rung is «not filled», not zero.

Partial closes

No partial close was recorded for this trade.

Event timeline

Times are shown in UTC; hover a timestamp to see the same instant in Tehran local time. The machine value in each `datetime` attribute is always UTC.

Timeline consistency check: Consistent

Every timestamp on this page is UTC. position_events.occurred_at is stored naive in Asia/Tehran local time and is converted here. The event log is written by the monitor loop immediately after it stamps positions.closed_at, so a closing event can trail the close by a few seconds; measured across the whole ledger on this snapshot, 14,573 timestamped events, none before the position opened, 31 after it closed across 28 position(s), the worst by 125s. Every such event is listed above with no tolerance applied; the 300s tolerance only decides whether this trade is flagged as inconsistent.

Execution quality