Lanky-Exception
0xe5fcaa220bf63116864beb10ab1e66b79de757b1
Wallet digest
Activity score
43/100
Performance: thin sample
Open positions
2
Open notional
$0.00
Total PnL
$-5.9K
Realised
$0.00
Win rate
n/a
too few closed
Recent activity
- REDEEMWill the highest temperature in Paris be 17°C or higher on March 1?$24.00Mar 2, 07:20 UTC
- TRADEBUYWill the highest temperature in Paris be 17°C or higher on March 1?$23.76Mar 1, 01:40 UTC
- TRADEBUYWill the highest temperature in London be 10°C on January 22?$1.3KJan 22, 07:56 UTC
- TRADEBUYAdelaide International: Jaqueline Cristian vs Ekaterina Alexandrova$2.8KJan 12, 02:20 UTC
- TRADEBUYAdelaide International: Jaqueline Cristian vs Ekaterina Alexandrova$1.8KJan 12, 02:19 UTC
- REDEEMWill Satoshi move any Bitcoin in 2025?$101.20Jan 7, 11:34 UTC
- TRADEBUYWill Satoshi move any Bitcoin in 2025?$101.00Dec 31, 09:17 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)
- 5
- Avg trade size
- $1.2K
- Top category
- —
- Category concentration
- 0%
- First seen
- Dec 31, 09:17 UTC
- Last active
- Mar 2, 07:20 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".