ROUTE WATCH / 4663LIVE
SALE
COHORT
NEXT BUY
INDEXED EVENTSSCANNING ROUTEBLOCK 4663 · READ ONLY
LIVE INDEXWALLET ROTATION / ROBINHOOD CHAIN 4663
ONCHAIN ROTATION INTELLIGENCE
FOLLOW THE MONEY
AFTER IT LEAVES.
Paste a token. See what its sellers bought next, then inspect how those buyers connect to the next token’s deployer.
✓ NO WALLET REQUIRED✓ NO SIGNATURES✓ NO TRADES
SCOUT LOOP / CONTINUOUSTRACKING
A14B
14BSALE DETECTED+2m 04sNEXT BUY VERIFIED
SCOUT / ROUTE 01TRACE ACTIVE
SELLBUYLINK
ONCHAIN EVENTSSERVER-SIDE APINO SYNTHETIC DATA
MODE READ ONLYINPUT TOKEN CAOUTPUT NEXT PURCHASEEVIDENCE LITERAL LINKSDATA LIVE BLOCKSCOUT
01
LIVE ONCHAIN SCANNER
Trace a token rotation
Enter a full token contract on Robinhood Chain. TRAIL reads confirmed Blockscout events; the API key stays on the server.
Resolving sellers0%
Next tokenBuyersDeployer linksCombined valueStill holdingContract
03
Coverage pending
Evidence trail
SOURCESOURCE TOKENconfirmed sellers
soldconfirmed tx
COHORT0 WALLETSlive cohort
next buyordered by block
DESTINATIONDESTINATIONholding state
A sell tells you who left.
The next buy tells you what they believe.
Wallet tools usually stop at the source token. You see holders selling, but the trail disappears the moment capital moves elsewhere. Then the investigation splits across explorers, holder tables, deployer histories, funding graphs, and fee metadata.
TRAIL keeps that sequence intact. It follows each qualifying seller forward, groups confirmed next purchases, checks current balances, and compares recent direct buyer ↔ deployer transactions — without turning observations into an unexplained safety score.
01 SOURCE SALE02 NEXT PURCHASE03 CONTRACT ORIGIN04 HOLDING CHECK
PRODUCT WALKTHROUGH
One query. The complete route.
Each step answers a different research question. Together they show whether a rotation deserves a closer look.
Resolve real sellers
Choose a lookback window and isolate wallets that executed a qualifying sale of the source token.
Transfers excluded · duplicates removedFollow the next purchase
Advance each seller’s history until TRAIL finds the next qualifying market buy.
Order preserved · time delta recordedGroup the destinations
Rank new tokens by rotating wallets, combined buy size, latest activity, and current holding state.
Cohort strength · capital concentrationVerify origin and links
Read the indexed creator address, current buyer balances, and any direct buyer ↔ deployer transaction found in the latest scanned history.
Literal labels · explicit coverage limitstrail://rotation/liveCHAIN 4663
01 qualifying_sales.resolve(source, window)02 next_purchase.follow(wallets)03 destinations.group(by: cohort + size)04 evidence.check(origin + direct_tx + balance)
RESULTLIVEconfirmed events onlycoverage disclosed
EVIDENCE LANGUAGEShow what happened.
Show what happened.
Never invent who owns it.
TRAIL labels observable relationships literally, so the user can separate a fact from an interpretation.
↔
STRONG OBSERVATIONDirect transfer
Funds moved directly between a selected buyer and the destination token’s deployer.
Shows a transaction · does not prove common control⌁
INDEXED ORIGINContract deployer
The creator address returned by Blockscout for the destination contract.
Shows indexed origin · identity remains unknown◉
CURRENT STATEBalance check
The latest indexed token balance for every analyzed buyer wallet.
Shows current balance · not continuous conviction∅
NO MATCH FOUNDNo detected connection
The selected sources and block range returned no matching relationship.
Shows search outcome · not proof of independenceHOW TO READ THE RESULT
Four layers. No invented score.
The live result separates what is confirmed, what is currently indexed, and where the scan has a hard coverage limit.
ORIGIN / LIVE
Start from the indexed creator address.
TRAIL asks Blockscout for the destination contract’s origin and compares that deployer with the latest 100 indexed direct transactions of each buyer.
- Exact destination contract retained
- Indexed creator address shown literally
- No ownership inference added
BUYERSconfirmed cohortTOKENexact contractDEPLOYERindexed origin
TXBALANCETIME
COHORT / LIVE
Group only verified next purchases.
Each buyer must first pass the sale rule, then show token outflow and net receipt of a non-quote token in a later confirmed transaction.
- Plain transfers excluded
- Transactions ordered by block and time
- One next destination per analyzed seller
TXevent-based
COVERAGE / EXPLICIT
Limits remain visible beside the result.
The live version caps source pagination, fully analyzes up to four qualified sellers, and reports whether that cap affected the scan.
- Up to 100 recent source transfers
- Up to 4 qualified sellers per scan
- Up to 24 hours to find the next purchase
BALANCE / LATEST
Show current indexed state, not a narrative.
For every destination cohort, TRAIL checks the latest token balance of each analyzed buyer.
- Positive balance: still holding
- Zero balance: no current holding
- Unavailable: shown as unknown
HOLDINGYES
ZERONO
UNKNOWN?
RESEARCH MOMENTS
Built for the decision after the sell.
TRAIL does not tell you what to buy. It shows which destination deserves investigation and which questions to ask next.
Find the next cluster
Your token loses several familiar wallets. TRAIL groups their next purchases and reveals whether the flow is scattered or converging on one destination.
Watchbuyers after exit · combined size · last purchase
Inspect direct overlap
A new token attracts the same wallets. TRAIL checks recent direct buyer ↔ deployer transactions and keeps the matching transaction hashes.
Watchdirect transactions · deployer origin · explicit history cap
Check whether tokens remain
The first rotation may already be over. TRAIL reads the latest indexed token balance for every analyzed buyer.
Watchpositive balance · zero balance · unavailable checks
DATA PIPELINE
From block activity to a reviewable trail.
Every transformation keeps a route back to the public event that produced it.
Normalize
Blocks, transactions, logs, token metadata, and launch records.
Classify
Qualifying buys and sells separated from ordinary transfers.
Sequence
Each seller followed forward to the next verified purchase.
Connect
Contract origin, direct buyer ↔ deployer transactions, and current balances.
Verify
Coverage, timestamps, source references, and missing-data flags.
PRODUCT BOUNDARY
Research infrastructure, not a black-box signal.
The first release is deliberately narrow: move quickly from a known source token to the next destination, then inspect the evidence without giving custody or execution authority to the product.
TRAIL DOESTRAIL DOES NOT
Resolve qualifying sellersImport private keys
Identify next verified buysExecute or sign trades
Expose direct deployer linksProve wallet ownership
Check latest indexed balancesGuess unobservable intent
Show coverage and uncertaintyGuarantee token safety
DELIVERY ROADMAP
Build the trail in measurable layers.
Performance claims arrive only after reproducible tests against indexed public-chain history.
Evidence contract
Event definitions, relationship labels, data boundaries, and interface studies.
COMPLETELive rotation scan
Blockscout-backed seller resolution, next-purchase sequencing, grouping, balances, and direct links.
LIVELaunch graph
Deployer histories, observed funding paths, fee recipients, and concentration.
PLANNEDLive workspace
Streaming updates, saved trails, material-change alerts, and measured latency.
PLANNEDFAQ
Read the output correctly.
Does a deployer connection mean the wallets share an owner?+
No. TRAIL reports a direct indexed transaction between a buyer wallet and the destination contract’s creator address. That fact can guide research, but it does not establish legal or beneficial ownership.
Why are ordinary token transfers excluded?+
Receiving tokens is not automatically a market purchase. Excluding plain transfers prevents airdrops, internal movements, and distributions from being mistaken for buyer conviction.
What does “no connection detected” actually mean?+
It means the selected sources, block range, and relationship rules returned no match. It does not prove that two parties are independent, which is why coverage remains visible.
Can TRAIL trade or hold funds for me?+
No. TRAIL is designed as a read-only research workspace. It does not import private keys, sign transactions, execute orders, or promise financial outcomes.
FOLLOW THE ROTATIONThe trail is already there.
The trail is already there.
TRAIL makes it readable.
Start from a token you know, follow confirmed sellers to their next purchase, and inspect the exact onchain evidence before deciding what deserves deeper research.
Run a live scan ↗