1,534,114 launches on record
Coverage from 2 Sep 2026
Archive read 15:49 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

OUROCHAT

Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record - a marker being one of the launch-record tests below that fired - and none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.

Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 creator wallets in all, and this creator has 1,518 other launches on record. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 47% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.

7kQ4KabG7CTiat3qjKuury3ZeTf33PiWp4Jgx39mpump Solscan pump.fun

Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.

noteOnly 16.1 SOL of liquidity was in the pool just now.

At launch

Created2026-09-26 07:31 UTC
CreatorD9gQ6RhKEpnobPBUdWY5bPQt2p3zGk3iVz6ChpUi2ArA
Creator took9.6% of supply in the first block
Outside buyers371 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 149 within the first 30s, 8 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated3 min after launch
Curve on chainNot re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers.
Creator soldnot while we watched
Recorded from389ajtC1eoJbMoiSbjhH4n… slot 450,607,974
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Order of events

Created2026-09-26 07:31:27 UTC
Slot 450,607,974, which is the chain's own clock for this moment.
Creation block8 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in149 distinct buyers, within the first thirty seconds.
A snapshot taken off a tick at the thirty-second mark, so it carries no moment of its own; it is placed here because that is where it happened.
Curve completed2026-09-26 07:34:43 UTC +3m 17s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-09-26 07:34:43 UTC +3m 17s
4.109e-7 SOL per token. Decoded from an on-chain transaction that executed at that price. A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not here.

Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.

Seen before

This pictureOn 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 47% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 14 launches from 11 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 86.5% wear one that more than one creator wallet has launched. See this ticker's page →
This creator1,518 earlier launches, 48 confirmed complete on chain, 12 with findings on record. Across the archive, 71.5% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 779 other creator wallets, across 1,314 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 58% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity16.1 SOL
Read from chain2026-10-07 17:16 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameOUROBOROS
DescriptionCreated on https://rapidlaunch.io @sierracatalina
Metadata heldsha256 0b27acd5036b862ec482ba4f907bcd8329e2cb0e687dc1d49f29fb3552840e76 · 323 bytes
Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree.
Document re-readByte-identical to the launch-time capture when re-read 2026-10-03 07:32 UTC.
Picture heldsha256 02e46ca5fcef71417a590a08385ca9341ae8ec6a363fca3b2d6e6f84b7214516 · 9,535 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-09-26 07:31 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another