Wild-Compliment
0xee907f9875f6afc9073df502c037b1ac90315dcb
Wallet digest
Activity score
81/100
Performance: thin sample
Open positions
2
Open notional
$4.1K
Total PnL
$96.81
Realised
$0.00
Win rate
n/a
too few closed
Recent activity
- YIELD$0.45May 18, 00:12 UTC
- YIELD$0.45May 17, 00:14 UTC
- YIELD$0.45May 16, 00:14 UTC
- YIELD$0.45May 15, 00:13 UTC
- YIELD$0.45May 14, 00:10 UTC
- YIELD$0.44May 13, 00:12 UTC
- YIELD$0.44May 12, 00:15 UTC
- YIELD$0.44May 11, 00:15 UTC
- YIELD$0.44May 10, 00:15 UTC
- YIELD$0.44May 9, 00:15 UTC
- YIELD$0.44May 8, 00:10 UTC
- YIELD$0.44May 7, 00:14 UTC
- YIELD$0.44May 6, 00:12 UTC
- YIELD$0.44May 5, 00:10 UTC
- YIELD$0.28May 4, 00:10 UTC
- YIELD$0.31May 3, 00:14 UTC
- YIELD$0.29May 2, 00:16 UTC
- YIELD$0.41May 1, 00:13 UTC
- YIELD$0.36Apr 30, 00:11 UTC
- YIELD$0.40Apr 29, 00:11 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)
- 2
- Avg trade size
- $2.0K
- Top category
- —
- Category concentration
- 0%
- First seen
- Apr 15, 06:24 UTC
- Last active
- May 18, 00:12 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".