Remote-Vehicle
0x1e68e1b5f549de2a232f128c1e8b7d3d16e30485
Wallet digest
Activity score
79/100
Performance: thin sample
Open positions
1
Open notional
$101.88
Total PnL
$-0.36
Realised
$0.00
Win rate
n/a
too few closed
Recent activity
- TRADEBUYWill Ethereum reach $2,400 on May 24?$102.25May 24, 10:24 UTC
- TRADESELLWill Bitcoin dip to $66,000 May 18-24?$2.46May 24, 02:26 UTC
- TRADESELLWill Bitcoin dip to $66,000 May 18-24?$99.79May 24, 02:26 UTC
- TRADEBUYWill Bitcoin dip to $66,000 May 18-24?$102.16May 22, 09:02 UTC
- TRADESELLWill the price of Bitcoin be above $70,000 on May 23?$102.16May 22, 00:19 UTC
- TRADEBUYWill the price of Bitcoin be above $70,000 on May 23?$102.07May 21, 08:26 UTC
- TRADESELLWill the price of Ethereum be above $2,500 on May 22?$102.08May 21, 00:16 UTC
- TRADEBUYWill the price of Ethereum be above $2,500 on May 22?$101.99May 20, 17:27 UTC
Persistent ledger timeline
persistentNo trades for this wallet in Orrery's persistent ledger yet. The whale-ingest cron writes ≥ $5k trades every 10 minutes; check back after a recovery window.
Ledger intelligence
persistent7d volume
$0.00
0 trades
30d volume
$0.00
0 trades
Buy share
50%
Sample
low
0 ledger trades
No persistent whale trades for this wallet yet. The live Data API score above can still be useful, but the durable ledger sample is empty.
Profile dimensions
Trade count + how recently they were active. Low = dormant.
How trustworthy the win-rate number is, based on sample size of closed markets.
Share of trades concentrated in their top category.
Share of positions taken while the market was still uncertain (30–70¢) rather than after direction was obvious.
How risky to blindly copy. Higher = riskier — large size, single-position exposure, or thin win-rate sample.
- Trades (all time)
- 8
- Avg trade size
- $89.37
- Top category
- —
- Category concentration
- 0%
- First seen
- May 20, 17:27 UTC
- Last active
- May 24, 10:24 UTC
- Win rate sample
- 0 closed
The single Activity score is kept for the leaderboard sort. The five dimensions above are the canonical read — copy-risk bar is inverted so green is always "better for the user".