Lucky-Void
0x1fe42c24a5265f7b2412ae7a561040a79cd293a8
Wallet digest
Activity score
69/100
Performance: thin sample
Open positions
2
Open notional
$28.76
Total PnL
$2.35
Realised
$0.00
Win rate
n/a
too few closed
Recent activity
- YIELD$0.00Mar 28, 00:28 UTC
- YIELD$0.00Mar 26, 00:16 UTC
- YIELD$0.00Mar 24, 00:24 UTC
- YIELD$0.00Mar 23, 00:24 UTC
- YIELD$0.00Mar 22, 00:34 UTC
- YIELD$0.00Mar 21, 00:18 UTC
- YIELD$0.00Mar 20, 00:14 UTC
- YIELD$0.00Mar 19, 00:56 UTC
- YIELD$0.00Mar 18, 00:46 UTC
- YIELD$0.00Mar 17, 00:29 UTC
- YIELD$0.00Mar 16, 00:38 UTC
- YIELD$0.00Mar 15, 00:37 UTC
- YIELD$0.00Mar 14, 00:24 UTC
- YIELD$0.00Mar 13, 00:37 UTC
- YIELD$0.00Mar 12, 00:50 UTC
- YIELD$0.00Mar 11, 00:37 UTC
- YIELD$0.00Mar 10, 00:56 UTC
- YIELD$0.00Mar 9, 00:39 UTC
- YIELD$0.00Mar 8, 00:31 UTC
- YIELD$0.00Mar 7, 00:54 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)
- 0
- Avg trade size
- $0.00
- Top category
- —
- Category concentration
- 0%
- First seen
- Feb 4, 00:59 UTC
- Last active
- Mar 28, 00:28 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".