Grand-Battle
0xbd591c8cdb6bf6d278732840fcbc91cd94d06910
Wallet digest
Activity score
44/100
Performance: thin sample
Open positions
2
Open notional
$0.00
Total PnL
$-3.00
Realised
$0.00
Win rate
n/a
too few closed
Recent activity
- REDEEMWill $BTC reach 70k in July?$1.33Aug 14, 09:37 UTC
- REDEEMWill Noah Lyles (USA) win Gold in 100m?$9.52Aug 7, 09:51 UTC
- TRADESELLWill Elon Musk give a speech at Bitcoin conference? $0.58Jul 27, 20:31 UTC
- TRADEBUYWill Bitcoin hit $250k in 2024?$0.79Jul 27, 16:07 UTC
- TRADEBUYWill $BTC reach 70k in July?$1.00Jul 27, 15:50 UTC
- TRADEBUYWill Elon Musk give a speech at Bitcoin conference? $1.00Jul 27, 15:47 UTC
- TRADEBUYWill a presidential candidate say Mog at BTC conference?$1.00Jul 27, 15:45 UTC
- TRADEBUYWill $ETH reach 3.7k in July?$2.00Jul 27, 15:38 UTC
- TRADEBUYWill Noah Lyles (USA) win Gold in 100m?$4.00Jul 27, 15:31 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)
- 7
- Avg trade size
- $1.48
- Top category
- —
- Category concentration
- 0%
- First seen
- Jul 27, 15:31 UTC
- Last active
- Aug 14, 09:37 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".