on-chain proof

Every onboard, on the record.

One wallet funds in-person Solana onboards. Every transfer out of it lands here live, straight from the chain — along with what each recipient did next. Nobody has to trust the story.

Watching wallet BAPe…tRK9
Every number below is on-chain. Click anything to verify. Wallet: BAPe423B…5mtRK9
⚠ Chain data is catching up. Showing the last synced state.
Onboards
Unique wallets
$BASED distributed
Still holding
Activity

Onboards per day

Each bar is a day. Full history of this wallet.

Consistency

Onboard days since the wallet went live.
none123+
Where the tokens stand

Recipient status mix

Neutral by design. Someone who sold is a data point, not a villain.
Every wallet, one picture

The bubble field

One bubble per recipient. Size = current $BASED balance, color = status. Click a bubble for its full history.

Where it all went

Every token distributed, traced to where it stands today.
Live feed
Every onboard
Date Recipient Amount USD at send Holds now Status Tx
About this data

This page tracks one thing: outbound transfers of $BASED from the public onboarding wallet, and what each receiving wallet did afterward. It reads the chain directly. There is no manual bookkeeping between you and the numbers.

How statuses are computed

holding keeps ≥90% of what was received · accumulated holds more than received · partial exit keeps 10–90% · full exit under 10% via a swap · transferred moved out without selling · dormant no activity of any kind for 90+ days.

What is deliberately not shown

No names, photos, or socials are ever attached to recipient wallets. Wallets appear truncated with explorer links — everything shown is already public on-chain. If a wallet is yours and you want it masked from this view, ask via @DevBasedSolana and it will be honored.

Honesty notes

USD-at-send is only recorded when a live price existed at ingest time — older events show a dash instead of a guess. Some outbound transfers are ops, not onboards (paying a dev, moving treasury); those are reclassified by the admin and the count of reclassifications is shown below. The tracker itself can lag; the timestamp below is the truth about freshness.