Leading-Cyclone
0x0dbb002d5b7a28b11c40cfcd14814c4bfeace5bc
Wallet digest
Activity score
82/100
Performance: thin sample
Open positions
2
Open notional
$2.9K
Total PnL
$-17.68
Realised
$0.00
Win rate
n/a
too few closed
Recent activity
- YIELD$0.31May 18, 00:16 UTC
- YIELD$0.31May 17, 00:13 UTC
- YIELD$0.31May 16, 00:14 UTC
- YIELD$0.31May 15, 00:11 UTC
- YIELD$0.31May 14, 00:10 UTC
- YIELD$0.31May 13, 00:15 UTC
- YIELD$0.31May 12, 00:14 UTC
- YIELD$0.31May 11, 00:15 UTC
- YIELD$0.31May 10, 00:12 UTC
- YIELD$0.31May 9, 00:14 UTC
- YIELD$0.31May 8, 00:15 UTC
- YIELD$0.31May 7, 00:13 UTC
- YIELD$0.31May 6, 00:12 UTC
- YIELD$0.31May 5, 00:14 UTC
- YIELD$0.20May 4, 00:11 UTC
- YIELD$0.22May 3, 00:12 UTC
- YIELD$0.20May 2, 00:12 UTC
- YIELD$0.26May 1, 00:10 UTC
- YIELD$0.25Apr 30, 00:10 UTC
- YIELD$0.25Apr 29, 00:12 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)
- 4
- Avg trade size
- $2.8K
- Top category
- —
- Category concentration
- 0%
- First seen
- Mar 4, 00:29 UTC
- Last active
- May 18, 00:16 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".