Ten wallets that buy the same token in the same second are not ten traders who agree. They are one keyboard. On a leaderboard they look like ten independent winners, and that is exactly the point of running them. This guide is about spotting the set before you copy any of it.
The thresholds in this guide are the ones Ocinct runs in production since September 2026. Buys in the same slot, about 270 milliseconds as measured on the chain since 18 September 2026, are the same hand. A leader has to be first on half the shared tokens and clearly ahead of the second. The minimum before the tool says anything at all is 3 shared tokens [1].
What is a crew of wallets on Solana?
A crew is a group of wallets operated together. The reasons vary. It may be to make a launch look like demand, to hold more of a supply than one wallet could without drawing attention, to place several wallets on a leaderboard so that one of them gets copied, or simply because the operator rotates wallets and keeps a few alive at once.
Whatever the reason, a crew has three properties you can measure.
How do you detect wallets that move together?
Three signals give a crew away. They are a shared funder, buys in the same second, and a stable leader that always trades first.
A shared funder
Crews are set up in a batch. One relay wallet sends 1 to 3 SOL to each member within minutes. Open the Funded by line on each wallet and the same address comes back. This is the cheapest check, and it catches most of the naive crews. An Ocinct scan card shows that first funder on Pro and Elite, token traders groups a token's traders by it, and how to read the label covers the details.
Sophisticated operators fund each wallet from a different exchange withdrawal. That defeats the funder check and leaves the next two.
Same second buys
Two humans do not buy the same token within one second of each other more than once by accident. One script does it every time. Pull the recent activity of the suspect wallets, line up the timestamps on shared tokens, and count how often the gap is under a second.
Ocinct orders the buys by slot rather than by timestamp. A provider rounds to the second, a slot lasts about 270 milliseconds since 18 September 2026, 317 before, measured on the chain, so two buys in the same second can still be ordered. Two buys in the same slot cannot, and the tool says so instead of inventing a leader. Repeated across at least three tokens, that is one operator.
A stable leader
The softer version is a follower, not a twin. Wallet B buys 10 to 90 seconds after wallet A, on token after token, and never before. That is a copy bot, or the operator's own second wallet firing after the first. Either way, copying B means paying for A's signal twice.
Ocinct measures the share of first places across shared tokens, not the reaction time. A crew enters minutes apart, so the leader is the wallet that arrives first again and again. It has to be first on half the shared tokens, and at least one and a half times more often than the runner up. Measured on a real group of three in September 2026, the leader was first on 61 percent of the tokens all three bought and the next on 21 percent. Anything closer than that is called no leader.
How do crews inflate leaderboards?
By running many wallets on the same launches and letting chance put a few of them at the top. Run twenty wallets on the same launches. Sell most of them into the buyers you attracted. Some wallets will end up with bad records and some with great ones; that is variance, not skill. Now the top three are on a leaderboard sorted by PnL, and nobody sorts by funder.
Copy one of the three and you copy a coin flip with the losing side hidden. Worse, on the next launch the crew's sells are the ones you buy from.
How do you keep crews off your copy list?
- Scan the list, not the wallet. When you pull the top traders of a token, look at the funder column before the profit column. Group by funder. Anything with three or more members is one entry, and usually not a good one.
- Check timing on the survivors. For the wallets that pass your filters, run who copies who or compare their recent buys by hand. Same slot buys or a fixed leader means drop the followers.
- Distrust perfect sets. Five wallets with 80 percent win rates that all trade the same twelve tokens are a set. Real independent traders overlap on the big tokens and diverge on the rest.
Which tools find wallets that move together?
On Pro and Elite, the token traders tool returns the traders of any token with their profit, tags and funder, and groups the ones that share a funder. Who copies who takes one wallet or a group of up to ten and reads the chain for same hand pairs, who buys first, and the wallet outside your list that all of them follow. A name is only printed when it beats a control window placed five minutes earlier, so a crowd of snipers is never mistaken for a source. Who copies who runs on tool credits, token traders costs one scan, and a run that fails is refunded.
By hand it is slower but the same work. Funder first, timestamps second, leader third.
Questions
How do you find linked wallets on Solana?
Look for a shared funder, buys within the same second on the same tokens, and a wallet that always trades just after another. Start with the funder, and group a list by funder before you read its profits.
Why do crews show up on leaderboards?
Twenty wallets on the same launches produce a few great records by chance. The leaderboard shows them as separate traders; they are one operator's variance.
Should you copy a wallet that is part of a crew?
Usually not. Treat the group as one wallet, since its combined record is one person's, and copying one member can make you the exit for the others.
Which Ocinct tools find crews?
Token traders groups a token's traders by the wallet that funded them. Who copies who takes up to ten wallets and says which one buys first, or that none leads.
Sources
[1] Ocinct, who copies who, thresholds as coded in the bot, https://www.ocinct.com/who-copies-who
[2] Helius, Wallet API, Funded by, wallet clusters and Sybil detection, https://www.helius.dev/docs/wallet-api/funded-by