What this launch shares with other launches
Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for five lists, or with Brand Protection at $79 a month for every list on every record. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.
Its own first blocks
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-11 01:54 UTC |
| Creator | GCPDYocGX2hwBVQEEWF9BWBNsuSbScMpapdhtpF95dw5 |
| Creator took | 3.0% of supply in the first block |
| Outside buyers | 1 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: 0 within the first 30s, 4 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 | 6.8 days 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 | 2UcXjKSFq8TuHAXodCtEEg… slot 455,476,649
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-11 01:54:11 UTC Slot 455,476,649, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | No buyer, 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-17 20:34:10 UTC +6d 18h Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-17 20:34:10 UTC +6d 18h
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 | No other launch we hold a picture for used this one. |
| This ticker | On 76 launches from 73 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.6% wear one that more than one creator wallet has launched. See this ticker's page → |
Pool
| Liquidity | 29.6 SOL |
| Read from chain | 2026-11-14 17:43 UTC, just now |
What this launch claimed to be
| Name | ShibaBlazeCoin |
| Description | The blaze meme of Shiba coin, ShibaBlazeCoin |
| Metadata held | sha256 02fe6fb407e87161c7b212a252c08a9dc1d071e342b9df3a07b2c38a790567a3 · 239 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-22 15:30 UTC. |
| Picture held | sha256 93821b777305c9cdcf0a613e800110575fac00c8fd8eea8ad18d0a82fd167d2f · 79,911 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-11 01:54 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.