Dramatic-Litigation
0xcf24de0aa0e6fffd791055614bec85a5717d4391
Wallet digest
Activity score
45/100
Performance: thin sample
Open positions
2
Open notional
$0.00
Total PnL
$-2.3K
Realised
$0.00
Win rate
n/a
too few closed
Recent activity
- TRADESELLWill the price of Ethereum be above $1,700 on February 26?$1.01Feb 26, 11:24 UTC
- TRADESELLWill the price of Ethereum be above $1,700 on February 26?$0.09Feb 26, 10:53 UTC
- TRADEBUYWill the price of Ethereum be above $1,700 on February 26?$1.10Feb 26, 08:36 UTC
- TRADEBUYXRP Up or Down on February 20?$4.40Feb 19, 17:24 UTC
- TRADEBUYXRP Up or Down on February 20?$1.0KFeb 19, 17:04 UTC
- TRADEBUYXRP Up or Down on February 20?$1.0KFeb 19, 17:03 UTC
- TRADEBUYEthereum Up or Down - February 18, 2:00PM-2:15PM ET$250.00Feb 18, 18:24 UTC
- TRADEBUYEthereum Up or Down - February 18, 2:00PM-2:15PM ET$25.00Feb 18, 18:24 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)
- 8
- Avg trade size
- $285.20
- Top category
- —
- Category concentration
- 0%
- First seen
- Feb 18, 18:24 UTC
- Last active
- Feb 26, 11:24 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".