35.5%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
128launches carry this ticker, from 99 creator wallets20other launches used this exact picture file
The creator took 35% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
Also recorded, and not part of the finding above: this picture is on 20 other launches from 4 creator wallets in all, and this creator has 298 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, 56.2% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
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.
noteThe creator took 35.5% of supply at launch.
noteThe creator sold while we were watching.
noteOnly 2.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-09 23:04 UTC |
| Creator | 7ufmve7ZSFCzuNcKRunYrGtyb2Ka1MXzkWwf7jZhVsmL |
| Creator took | 35.5% of supply in the first block |
| Outside buyers | unknown 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: 132 within the first 30s, 16 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. |
| Graduated | 7 min after launch |
| Curve on chain | Not 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 sold | yes |
| Recorded from | J9YbCmokVUc9UZjK86r5Ah… slot 445,731,169
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Order of events
| Created | 2026-09-09 23:04:15 UTC Slot 445,731,169, which is the chain's own clock for this moment. |
| Creation block | 16 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-09-09 23:04:15 UTC
4.109e-7 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
| Thirty seconds in | 132 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 completed | 2026-09-09 23:10:54 UTC +6m 39s Confirmed: a PumpSwap pool was found for it. |
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 picture | On 21 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 128 launches from 99 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, 89.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| This creator | 298 earlier launches, 24 confirmed complete on chain, 3 with findings on record. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 284 other creator wallets, across 488 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, 64% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Pool
| Liquidity | 2.3 SOL |
| Read from chain | 2026-11-11 19:40 UTC, just now |
What this launch claimed to be
| Name | rawdog |
| Description | Launched on discord.gg/uxento |
| Metadata held | sha256 d0d79d670f508177ab72e8f4db3ce15819177c174631e295b432f746f407b2e8 · 346 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-read | Byte-identical to the launch-time capture when re-read 2026-09-17 17:28 UTC. |
| Picture held | sha256 8ae5730dc6e233409045050170f840db5de49f5114578ad1d80983e2a7fd1e80 · 16,356 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-09 23:04 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.