Unwilling-Fax
0x4314dbffe65bfff5c9b024fa0bb49b3ca0e37d74
Wallet digest
Activity score
45/100
Performance: thin sample
Open positions
3
Open notional
$0.00
Total PnL
$-2.2K
Realised
$0.00
Win rate
n/a
too few closed
Recent activity
- TRADEBUYSpread: Hawks (-13.5)$20.58Mar 23, 08:50 UTC
- REDEEMWill Bitcoin reach $150,000 in January?$2.31Mar 22, 04:31 UTC
- REDEEMSpread: Thunder (-21.5)$18.00Mar 22, 04:31 UTC
- TRADEBUYSpread: Thunder (-21.5)$9.36Mar 21, 09:13 UTC
- TRADEBUYWill Bitcoin reach $150,000 in January?$2.31Jan 27, 03:23 UTC
- REDEEMSpread: Knicks (-4.5)$2.5KJan 18, 07:55 UTC
- TRADEBUYSpread: Nuggets (-13.5)$763.28Jan 17, 13:05 UTC
- TRADEBUYSpread: Knicks (-4.5)$1.4KJan 17, 13:00 UTC
- TRADEBUYSpread: Mavericks (-4.5)$1.3KJan 17, 12:57 UTC
- TRADEBUYSpread: Mavericks (-4.5)$140.40Jan 17, 12:57 UTC
- TRADEBUYSpread: Mavericks (-4.5)$2.70Jan 17, 12:53 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
- $449.50
- Top category
- —
- Category concentration
- 0%
- First seen
- Jan 17, 12:53 UTC
- Last active
- Mar 23, 08:50 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".