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
Also recorded, and not part of the finding above: this picture is on 164 other launches from 89 creator wallets in all. 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.5% 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.
At launch
| Created | 2026-11-10 05:32 UTC |
| Creator | ECw5EbEP7fZ4xaGP5vaQJoopAJ8yrFdKwCGtg2L4kdY6 |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 6 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: 6 within the first 30s, 6 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 | 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 | 2KykVyJBZ6WQiuNJrtQ6Jq… slot 467,604,033
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-10 05:32:50 UTC Slot 467,604,033, which is the chain's own clock for this moment. |
| Creation block | 6 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-11-10 05:32:50 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 6 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. |
| Highest price seen | 2026-11-10 07:57:23 UTC +2h 24m 33s
2.348e-6 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 165 launches from 89 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.5% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 2,245 launches from 1,278 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 | 0.6 SOL |
| Read from chain | 2026-11-14 11:53 UTC, just now |
What this launch claimed to be
| Name | FLOAT |
| Metadata held | sha256 134c08f1b08be390f563dfe52e0bebcbf93a9b4dc9296dd838fb9bbe5640f9bc · 253 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-11-11 05:33 UTC. |
| Picture held | sha256 d00fb4ef05c8c50ab7a913afe15124c38cffda9579b2c9d36cb3f1d48ccb4b27 · 1,228,876 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-10 05:32 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.