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 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. 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 10 other launches, and this creator has 130 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.
| Its most recent other launches (UTC) | Ticker | Name | Mint |
|---|---|---|---|
| 15 Nov, 16:43 | P100X | PUMP.100X | ██████████ |
| 15 Nov, 16:32 | P100X | PUMP.100X | ██████████ |
| 15 Nov, 16:30 | P100X | PUMP.100X | ██████████ |
| 15 Nov, 16:24 | P100X | PUMP.100X | ██████████ |
| 15 Nov, 16:22 | P100X | PUMP.100X | ██████████ |
| 15 Nov, 15:40 | beer | beer | ██████████ |
| See all of this creator's launches → | |||
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-15 15:13 UTC |
| Creator | 4zG29JCiz98TxFsS1UyGtESaSnh8MfmFYYvWXQwXy7bu |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 29 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, 0 in the very same block the token was created in. |
| Graduated | 0 min after launch |
| Curve on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | yes |
| Recorded from | 3ypRSkZQtn9qQZE8P9vhxF… slot 469,775,797
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-15 15:13:50 UTC Slot 469,775,797, 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-11-15 15:14:12 UTC +22s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-11-15 15:14:12 UTC +22s
1.256e-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 | 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. |
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 creator | 86 earlier launches, 1 confirmed complete on chain. 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 2 other creator wallets, across 6 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, 63.7% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | KAI ATTACK |
| Description | He Protect he also attack |
| Metadata held | sha256 8bf6d2e6a2722c0a7d9d800816dd058dec35a5ee2be797fc2bca2656f3cb9973 · 218 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 ef415837c13e00a5897bb9e523c4da2ac7ef7c496a85315ca0d64d617bbdfcca · 234,029 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-15 15:13 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.