Launch
LIVE · solana mainnet · slot 451,425,612

A coin gets one shot at its own fees.

Point a token’s creator fees at an address that is not yours — once, because the program allows one. Yopay keeps every fee in four columns, and a figure is received when a claim says so, never before.

pointing them at an X handle is what this is for, and it works: a handle registers an address and proves it, then Assign fees resolves @handle to exactly that address. A handle that has not registered resolves to nothing — and registering takes about a minute

Launch on Pump Pons
$YOPAAkxLg5eTqqzxcJCBrTjF9ezRchkDvCgD6faz1DN6pump

the address is the only thing about the coin this site writes down: everything else is read from the chain

700,253

fee configurations on the Pump Fees Program

scanned whole at slot 451,425,120

1,360.55 SOL

held above the rent floor by those accounts

slot 451,425,120 · 637,549 of 700,253 hold more than the 0.005852 SOL floor

451,425,612

the slot this page was built at

reload and this moves · the scan above is 2 min old

PENDINGCLAIMABLERECEIVEDLAPSED

a payout that lapsed is LAPSED: never a smaller RECEIVED

8 that carry artwork, of 700,253 configurations · slot 451,425,120

ExploreOpen →

No payment has been made.

These four are the states a coin’s creator fee can be in. Nothing has reached any of them through Yopay yet.

PENDING 0on chain, belonging to nobody yet
CLAIMABLE 0addressed to someone who has not taken it
RECEIVED 0taken. The only state that counts as received
LAPSED 0lapsed, and gone back
PaymentsOpen →

Distinct balances

11

among 700,253 accounts · slot 451,425,120

8,017,92087.0%
5,852,1609.0%
7,295,6164.0%

no line. A series needs more than one scan

AnalyticsOpen →

Handles that have registered an address

0

read at 2026-09-28T20:24:53.934Z

Register once and your handle resolves to your address. Until then there is no address to route to. That is how the chain works, not a rule we made.

no search box here: it would resolve handles that have not registered, and those have nothing behind them yet

Register handleOpen →

One config account per mint

OFFLENFIELD
011discriminator
1132token mint
4332admin
751revoke flag
764shareholder count
80N×34shareholders

rendered from the constant the parser uses, re-derived against mainnet by probe-rail

Why it is called Yopay

A coin gets one shot at its own fees. The split can be written once per mint, and that is not a convention somebody agreed to. It is a check inside the program, which says so in its own words when you try it twice:

SharingConfigAdminRevoked. “sharing config authority has been revoked - sharing config can only be updated once.”

Read at slot 451,423,823: 523,251 coins on mainnet have already spent theirs and 176,994 have not.

74.7% of 700,245 configurations: spentone reading, at one slot · it is not counting up any more

So the question this site answers is not how much. It is whether it is still spendable.

Two kinds of once, never confused

A coin’s assignment: final

Written once, then the authority is revoked by the program itself. There is no undo, no support request, and nothing this site could do about it. It is spent or it is not.

A handle’s registration: revisable

Register again and the new address wins, while the old row stays on the record. The table is append-only, so a moved address leaves a history rather than erasing one.

the second never borrows the finality of the first. It would sound stronger and it would not be true

Top tokens by fees held

Pump Pons

ranked by SOL held, over all 700,253 configurations at slot 451,425,120, not a sample. A row marked tied shares its balance to the lamport with that many others, so its position is an ordering, not a rank.