TYR-260719-0TYW3NAV
SOLUSDT
+3.12% on margin
There is no dollar figure in this record: position size was never stored. The only unit available is percent.
Trade geometry
Stop, entry and the take-profit rungs
The prices recorded when the signal was sent. Rungs that actually filled are marked.
- Stop76.02
- Entry76.29
- TP174.23
- TP273.65
- TP373.08
- TP472.50
- TP571.92
- TP671.35
Trade overview
Final return (% of margin)
Final return (% of margin): +3.12% (افزایش)Unleveraged price move (%)
+0.260% (افزایش)Leverage
12xHolding time
5h 40m- Signal entry price
- 76.29
- Entry trigger price
- 76.24
- Stop loss
- 76.02
- Implied exit price
- 76.09
- Observed exit price
- 76.03does not reconcile with the recorded return
- Exit reason
- SL
- Signal created
- Activated
- Closed
observed_exit_price is the market price seen when the exit condition was detected. The recorded ROI is booked at a modelled stop fill of sl +/- 0.10%, so on stop exits the two do not match. Aggregates use the recorded ROI only.
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.
| Rung | Target price | Filled | Return at fill | Filled at | Telegram reply |
|---|---|---|---|---|---|
| TP1 | 74.23 | Not filled | در دسترس نیست | not available | — |
| TP2 | 73.65 | Not filled | در دسترس نیست | not available | — |
| TP3 | 73.08 | Not filled | در دسترس نیست | not available | — |
| TP4 | 72.50 | Not filled | در دسترس نیست | not available | — |
| TP5 | 71.92 | Not filled | در دسترس نیست | not available | — |
| TP6 | 71.35 | Not filled | در دسترس نیست | not available | — |
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.
| Event | Time | Price | Return at that moment | Telegram reply |
|---|---|---|---|---|
| ENTRY_TRIGGERED | 76.24 | در دسترس نیست | — | |
| SL_ADJUSTED | 76.02 | در دسترس نیست | — | |
| SL_HIT | 76.03 | +3.12% (افزایش) | — |
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
Entry latency
5sSlippage
-0.066%This trade is one of 1,156 published trades.