D_patientB🐂ll ◻️ profile picture

D_patientB🐂ll ◻️ wallet

@DPatient_Bull is a KOL tracked by CabalSpy on BNB Chain, Base, Ethereum and Robinhood Chain.No tracked trades in the last 30 days.

KOL Profile · data as of October 2, 2026

D_patientB🐂ll ◻️'s wallet address

EVM wallet

0x0d1d0219e39595d34990cb711ee58c7ce7047291
Chain30d PnLWin rateTradesVolume
BNB ChainNo tracked trades in the last 30 days
BaseNo tracked trades in the last 30 days
EthereumNo tracked trades in the last 30 days
Robinhood ChainNo tracked trades in the last 30 days

About this profile

D_patientB🐂ll ◻️ (@DPatient_Bull on X) is listed in the CabalSpy database of labeled KOL wallets. CabalSpy tracks one wallet for this trader on BNB Chain, Base, Ethereum and Robinhood Chain. The figures above cover the last 30 days and were last updated on October 2, 2026; the live wallet page shows current trades, holdings and a PnL chart.

Realized PnL is sales minus purchases, so a wallet that still holds its tokens can show a loss it has not actually taken. Developers can query this wallet through the KOL API, the SDKs or the MCP server.

Questions

01

What is D_patientB🐂ll ◻️'s wallet address?

CabalSpy tracks one wallet linked to D_patientB🐂ll ◻️ (@DPatient_Bull): 0x0d1d0219e39595d34990cb711ee58c7ce7047291 (EVM: BNB Chain, Base, Ethereum and Robinhood Chain).

02

How can I follow D_patientB🐂ll ◻️'s trades?

Open the live wallet page on CabalSpy for current trades, holdings and PnL, or stream every buy and sell in real time through the CabalSpy KOL API (WebSocket stream "tx"). The wallet can also be looked up through the CabalSpy MCP server from Claude or Cursor.

03

How does CabalSpy link wallets to KOLs?

CabalSpy combines on-chain activity analysis, its KOL connections network and wallets the traders have made public themselves. Labels are verified before they are listed. If a wallet is attributed incorrectly, contact contact@cabalspy.xyz.

More KOL wallets

Track every KOL in your own product. Free API key, no credit card.

3,000+ labeled wallets on five chains via REST, WebSocket, SDKs and MCP.