the chain writes
the story.

forensic screening for any Solana token. every wallet named, every number linked to the transaction behind it.

— live log terminal —
LOG TERMINALLIVE
STATUSVERIFIED
CHAPTER 1471
The repeater is back. 20 SOL into $ANSEM for 6,043.84 tokens — the exact amount it bought last time before selling. The wallet carries a COPY_CASCADE label across other tokens. Three buys, three sells, same size each round. At some point a pattern stops being coincidence and starts being a system.
tx: V7kTWQ1N
case file / 00

what is this, actually?

LOG watches wallet activity for a token and turns what really happened into a short story, one chapter at a time — a big buy, a quiet exit, the same wallet showing up at 2am three nights running. Nothing is invented. Every chapter links to the transaction that caused it, so you can check it yourself in seconds.

what it actually does

four things, no filler

case file / 01

The Feed

Live chapters posting as things happen on-chain. Every one links straight to the transaction that caused it. If the chain didn't do it, the log doesn't say it.

verified
case file / 02

Forensic screening

Who bundled the launch, who sniped it, who the deployer paid, how concentrated it is now. Each percentage ships with the wallet addresses behind it, because the addresses are the part you can check. Anything we couldn't establish says so — it never renders as a clean zero.

live
case file / 03

Pre-Buy Check

Paste a contract address, get the forensic read back. Holders, concentration, who is coordinated, and what the contract still permits. No account, no charge, no limit.

free
case file / 04

Wallet memory

A wallet that sniped a launch in August is recognised the moment it turns up on a different token in December — not because we watched that token, but because we watched that wallet. A fresh address doesn't clear the record.

live
recent entries

the feed doesn't sleep. it just doesn't talk unless it's worth it.

CH.1471
The repeater is back. 20 SOL into $ANSEM for 6,043.84 tokens — the exact amount it bought last time before selling. The wallet carries a COPY_CASCADE label across other tokens. Three buys, three sells, same size each round. At some point a pattern stops being coincidence and starts being a system.
on-chain
CH.1470
The wallet labeled COPY_CASCADE just bought 6,049 $ANSEM for 20 SOL. This is the fourth time in as many chapters it has cycled through the same token—buy, sell, buy again, sell again. The pattern holds. No entry price is on record, so the outcome remains unknown; what is visible is the commitment to repetition itself.
on-chain
CH.1469
copy_cascade bought back in at 50 SOL, matching the entry size from two chapters ago. The wallet has now cycled through buy, sell, buy in a rhythm tight enough to read. No prior entry price is on record for this one, so the direction stays unknown — but the repetition itself is the data: this is not a one-off trader, it is a shape.
on-chain
the public record

Every token we screen stays screened, in public.

permanent
THE FORENSIC LAYER · NO ACCOUNT
The forensic layer of every tracked token is permanent and public

The verdict, the block it was derived from and the wallets behind every number — so anyone can check it without an account and without trusting us. Every token added makes that record longer.

The stories and chapters on your watchlist are yours — the ongoing narration as your tokens move, delivered as it happens.

where we haven't looked it says so — never a clean zero
no exceptions
policy

the three rules that don't bend

  1. Nothing gets written that didn't happen. No fake wallets, no manufactured drama, no paid volume dressed up as a chapter. The premise dies the moment the input's fake.
  2. Name the wallet, and prove the claim. A wallet trades under the name its own owner chose on pump.fun, so that name is the subject of the sentence — with the address beside it. Anyone can call themselves anything; the address is the part you can check.
  3. An accusation rests on a relationship, never on a timestamp. Being early, being late, or being large proves nothing. Naming a wallet as part of a launch cohort takes something provable about how it is connected — a transfer from the deployer, a shared funding source, a token they ran together before.

check a contract before you buy it.

Paste any Solana contract address into the bot and get the forensic read back — holders, concentration, who is coordinated, and what the contract still permits. Free, no account, no limit.

The safety question stays free, permanently. The forensic layer of every tracked token is permanent and public — a record of who did what on Solana, that nobody has to trust us to read.

$LOG token · CA: coming at launch