Creator-fee reward routing, in the open
See where the
fees land.
Every trade on a launched coin throws off a creator fee. FeeRoute follows that fee from the launch wallet, through the router, to the creator's tip-wallet — and maps the whole route on live, on-chain data.
Read-only analytics. Nothing is minted, traded or custodied here. The SOL price and the on-chain transfers are live and real; the per-creator fee attribution is a transparent model, labelled where shown.
The route
Fee in. Split. Creator paid.
Four hops, each one a real place value moves on Solana. FeeRoute does not sit in the path — it reads it, so you can see the route the same way the chain does.
-
01
A trade pays a fee
Every buy and sell on a launched coin carries a small creator fee. It accrues in the coin's launch wallet, one transfer at a time.
-
02
The router splits it
At each payout the fee is divided by a rule — the creator, holders, a buyback. FeeRoute models the split openly and shows the share.
-
03
SOL lands in a tip-wallet
The creator's share arrives as plain SOL in their tip-wallet. That transfer is public — the explorer below reads real ones live.
-
04
You can audit all of it
Price, volume and transfers are pulled from public APIs with no key. The only modelled hop is attributing fees to a creator, and it is marked.
Leaderboard
Creators, by fees routed
Live coins from DexScreener, grouped by the creator link on each. The coins, prices and volumes are real; fees routed is a transparent model — a 1% creator fee applied to the coin's live 24-hour volume. Pick a creator to see what launched for them.
On-chain, live
Routing explorer
Paste any Solana wallet — a launch wallet or a creator tip-wallet — and FeeRoute reads its most recent transactions straight from a public RPC, computing the real SOL that moved in or out of it. No key, no wallet, nothing signed.
Reading recent transactions…
Transfers are read live from Solana mainnet via a public RPC. Amounts are the net SOL change for the watched wallet in each transaction. Public RPCs rate-limit; if a read is throttled, FeeRoute shows a clearly-labelled sample so the view still makes sense.
Telemetry
Flow desk
The live numbers behind the route. Prices from Jupiter, coins and volume from DexScreener, transfers from Solana mainnet.
What this is, plainly
FeeRoute is a read-only concept and analytics view. It exists to make one idea legible: that creator fees are just SOL moving from one wallet to another, and that movement is public. The prices, coins and on-chain transfers shown here are live and real. The attribution of fees to a specific creator is a transparent model — a fixed fee rate applied to observed volume — and it is labelled wherever it appears. Nothing is minted, traded, custodied or paid out on this page, and no wallet is ever connected.
Questions
Straight answers
Which numbers are live, and which are modelled?
Live and real: the SOL price (Jupiter), each coin's price, market cap, volume and 24-hour trend (DexScreener), and every transfer in the routing explorer (read from Solana mainnet). Modelled: the "fees routed" figure per creator, which applies a fixed 1% creator-fee rate to a coin's live 24-hour volume. It is an illustration of scale, not a claim about a specific wallet's earnings, and it is labelled everywhere it shows.
Does FeeRoute move or hold any funds?
No. Nothing is minted, traded, custodied or paid out here, and no wallet is ever connected. FeeRoute only reads public data. The routing explorer reads a wallet's transactions; it never sends one.
How does the explorer compute an amount?
For each recent transaction it compares the wallet's balance before and after (the RPC returns both), and shows the net SOL change — positive if the wallet received, negative if it sent. That is the exact, on-chain delta, converted to USD at the live SOL price.
Where do "creators" come from?
From the links DexScreener publishes on each coin — an X handle or a website. Coins sharing a link are grouped under one creator. It is a best-effort grouping from public metadata, not an authenticated identity.
Why did a read come back as a sample?
Public Solana RPCs rate-limit heavy use. When a read is throttled, FeeRoute falls back to a clearly-labelled sample so the explorer still demonstrates the shape of the data. Reload in a moment to try a live read again.
Do you collect anything about me?
No accounts, no wallet connection, no tracking, no cookies. Everything runs in your browser against public APIs.