Also recorded, and not part of the finding above: this creator has 9 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. 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.
At launch
| Created | 2026-10-22 03:44 UTC |
| Creator | 8Fr85G1pEb3z9w31yALnJZjaB6rXamEuGHLDMZrnnKcX |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 28 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: 11 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 0 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 | not while we watched |
| Recorded from | 3U3G81nF79mLCwvzfc2MCr… slot 459,887,168
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-22 03:44:35 UTC Slot 459,887,168, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-10-22 03:44:55 UTC +20s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-22 03:44:55 UTC +21s
1.574e-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. |
| Thirty seconds in | 11 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. |
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 | No other launch we hold a picture for used this one. |
| This ticker | On 656 launches from 418 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 | 9 earlier launches. All 1 that reached the graduation threshold on our feed were read on chain, and none had completed. Across the archive, 70.6% of launches come from a creator with more than one launch on record. See the creator's launches → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-11-12 01:30 UTC, just now |
What this launch claimed to be
| Name | BTC |
| Metadata held | sha256 99b080ba773ae4857506f114cbeecf5cb303667d9c05e141433eeec2aa80c335 · 292 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-10-29 03:45 UTC. |
| Picture held | sha256 953137d318178f0eca9d40e6c3cbd7dc1c73e5fe1bd8c69e0011c96007fcbb8e · 77,680 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-22 03:44 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.