Previous-Submitter
0xf60d36f5eafc41a432fe9c39b7ab5a6e966c6085
Wallet digest
Activity score
35/100
Performance: thin sample
Open positions
2
Open notional
$0.00
Total PnL
$-500.49
Realised
$0.00
Win rate
n/a
too few closed
Recent activity
- REDEEMWho will win UFC 264: McGregor vs. Poirier?$0.00Jul 11, 05:34 UTC
- REDEEMWho will win UFC 264: McGregor vs. Poirier?$0.00Jul 11, 05:33 UTC
- REDEEMWho will win UFC 264: McGregor vs. Poirier?$208.49Jul 11, 05:33 UTC
- REDEEM(In-Game Trading) Who will win Bucks v. Suns: NBA Finals Game 2?$355.10Jul 10, 05:24 UTC
- REDEEMWho will win Bucks v. Suns: NBA Finals Game 2?$0.00Jul 10, 05:23 UTC
- REDEEM(In-Game Trading) Who will win Bucks v. Suns: NBA Finals Game 1? $253.62Jul 7, 20:45 UTC
- REDEEMWho will win Bucks v. Hawks: Eastern Conference Finals Game 5?$0.47Jul 4, 02:05 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
- Jul 4, 02:05 UTC
- Last active
- Jul 11, 05:34 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".