Thorny-Madam
0xaa5d3b055b0945f70d553c3dbf95e4f88520ab88
Wallet digest
Activity score
50/100
Performance: thin sample
Open positions
14
Open notional
$0.00
Total PnL
$-3.1K
Realised
$-1.18
Win rate
n/a
too few closed
Largest open positions
showing 10 of 14- YES
US strikes Iran by January 25, 2026?
30085 shares @ 2.3¢·now 0.0¢·exp Jan 31, 2026$0.00
$-678.87
- YES
US strikes Iran by January 29, 2026?
29665 shares @ 2.0¢·now 0.0¢·exp Jan 31, 2026$0.00
$-588.29
- YES
US strikes Iran by January 26, 2026?
11305 shares @ 2.1¢·now 0.0¢·exp Jan 31, 2026$0.00
$-242.47
- YES
US strikes Iran by February 24, 2026?
7674 shares @ 2.5¢·now 0.0¢·exp Jan 31, 2026$0.00
$-189.86
- YES
US strikes Iran by February 21, 2026?
6598 shares @ 1.4¢·now 0.0¢·exp Jan 31, 2026$0.00
$-94.92
- UP
Bitcoin Up or Down - February 11, 6:15PM-6:30PM ET
5992 shares @ 3.0¢·now 0.0¢·exp Feb 11, 2026$0.00
$-179.79
- YES
US strikes Iran by January 24, 2026?
3830 shares @ 1.3¢·now 0.0¢·exp Jan 31, 2026$0.00
$-49.79
- YES
US strikes Iran by February 10, 2026?
3758 shares @ 2.4¢·now 0.0¢·exp Jan 31, 2026$0.00
$-91.69
- PARIVISION
Counter-Strike: Vitality vs PARIVISION - Map 1 Winner
3437 shares @ 2.8¢·now 0.0¢·exp Feb 22, 2026$0.00
$-94.93
- DOWN
Bitcoin Up or Down - February 11, 7:00PM-7:15PM ET
2566 shares @ 32.0¢·now 0.0¢·exp Feb 12, 2026$0.00
$-821.25
Recent activity
- TRADEBUYUS strikes Iran by February 24, 2026?$49.94Feb 24, 22:28 UTC
- TRADEBUYUS strikes Iran by February 24, 2026?$45.00Feb 24, 21:51 UTC
- TRADEBUYUS strikes Iran by February 24, 2026?$94.93Feb 24, 19:56 UTC
- TRADEBUYCounter-Strike: Vitality vs PARIVISION - Map 1 Winner$94.93Feb 22, 16:44 UTC
- TRADEBUYUS strikes Iran by February 21, 2026?$94.93Feb 21, 20:05 UTC
- TRADEBUYUS strikes Iran by February 17, 2026?$1.83Feb 17, 23:01 UTC
- MAKER_REBATE$1.83Feb 12, 00:05 UTC
- TRADEBUYBitcoin Up or Down - February 11, 7:00PM-7:15PM ET$831.09Feb 12, 00:03 UTC
- TRADESELLBitcoin Up or Down - February 11, 6:45PM-7:00PM ET$843.86Feb 11, 23:59 UTC
- TRADEBUYBitcoin Up or Down - February 11, 6:45PM-7:00PM ET$920.12Feb 11, 23:46 UTC
- TRADESELLBitcoin Up or Down - February 11, 6:30PM-6:45PM ET$189.06Feb 11, 23:44 UTC
- TRADEBUYBitcoin Up or Down - February 11, 6:30PM-6:45PM ET$500.00Feb 11, 23:42 UTC
- TRADESELLBitcoin Up or Down - February 11, 6:30PM-6:45PM ET$1.2KFeb 11, 23:41 UTC
- TRADEBUYBitcoin Up or Down - February 11, 6:30PM-6:45PM ET$31.00Feb 11, 23:34 UTC
- TRADEBUYBitcoin Up or Down - February 11, 6:30PM-6:45PM ET$140.00Feb 11, 23:34 UTC
- TRADEBUYBitcoin Up or Down - February 11, 6:30PM-6:45PM ET$203.52Feb 11, 23:33 UTC
- TRADEBUYBitcoin Up or Down - February 11, 6:30PM-6:45PM ET$4.28Feb 11, 23:33 UTC
- TRADEBUYBitcoin Up or Down - February 11, 6:30PM-6:45PM ET$7.20Feb 11, 23:33 UTC
- TRADEBUYBitcoin Up or Down - February 11, 6:30PM-6:45PM ET$9.30Feb 11, 23:33 UTC
- TRADEBUYBitcoin Up or Down - February 11, 6:30PM-6:45PM ET$2.68Feb 11, 23:33 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)
- 49
- Avg trade size
- $113.17
- Top category
- —
- Category concentration
- 0%
- First seen
- Feb 11, 23:32 UTC
- Last active
- Feb 24, 22:28 UTC
- Win rate sample
- 1 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".