Medical-Wriggler
0x957725152166cfbf22521030bf0435ceb39618f5
Wallet digest
Activity score
43/100
Performance: thin sample
Open positions
3
Open notional
$0.00
Total PnL
$-3.3K
Realised
$0.00
Win rate
n/a
too few closed
Recent activity
- TRADEBUYSpread: Hawks (-13.5)$11.76Mar 23, 08:51 UTC
- REDEEMWill Bitcoin reach $150,000 in February?$5.00Mar 22, 04:46 UTC
- REDEEMWill Bitcoin reach $125,000 in February?$6.00Mar 22, 04:46 UTC
- TRADEBUYWill Bitcoin reach $125,000 in February?$5.98Feb 7, 05:02 UTC
- TRADEBUYWill Bitcoin reach $150,000 in February?$4.99Feb 7, 05:01 UTC
- REDEEM76ers vs. Hornets: O/U 226.5$650.00Jan 27, 06:45 UTC
- TRADEBUY76ers vs. Hornets: O/U 226.5$305.50Jan 26, 06:49 UTC
- TRADEBUYMagic vs. Cavaliers: O/U 228.5$421.92Jan 26, 06:39 UTC
- TRADEBUYSpread: Cavaliers (-5.5)$2.8KJan 26, 06:35 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)
- 6
- Avg trade size
- $597.62
- Top category
- —
- Category concentration
- 0%
- First seen
- Jan 26, 06:35 UTC
- Last active
- Mar 23, 08:51 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".