BLAST
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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.
noteThe creator sold while we were watching.
noteOnly 21.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 15:38 UTC |
| Creator | C8rLpLSU7uoLvFjBeEYgR6Q4FGxJTTPMmdwsf7mEjFAL |
| Creator took | 15.3% of supply in the first block |
| Outside buyers | 370 distinct wallets, not counting the creator, bought on the bonding curve: 63 within the first 30s, 1 bundled into the creation block. |
| Graduated | 4 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 4.1 h ago and it was finished. Checked 2026-10-02 16:01 UTC. |
| Creator sold | yes |
| Recorded from | 2C7AthSATQw5yt7gSsLYwJ… slot 452,652,897
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 15:38:17 UTC Slot 452,652,897, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 63 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-10-02 15:41:55 UTC +3m 38s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-02 15:41:55 UTC +3m 38s
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 picture | On 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 187 launches from 169 creator wallets, including this one. See them → |
| This creator | 115 earlier launches, 2 confirmed graduated on chain, 1 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 109 other creator wallets, across 106 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 21.7 SOL |
| Read from chain | 2026-10-02 20:06 UTC, just now |
What this launch claimed to be
| Name | BLAST |
| Description | Fees to @blast via UsePaid |
| Metadata held | sha256 2badd4993c7c9aa355a0d03292dc7a25af761302e7899e2c9a86f3f76650a8b0 · 412 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. |
| Picture held | sha256 ed2ff8d6172b4d8dedc7e04712e79c8ec7dbf3e8718086fb09a89d28391db4f7 · 5,536 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 15:38 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.