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 2 other launches from 3 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-13 03:10 UTC |
| Creator | FiGy6TB2CEU5MkN1XRTFWDaixHLe6qjTQDqrVyrMFtoD |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 406 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: 51 within the first 30s, 1 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 | 43 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 | yes |
| Recorded from | 2QoBwss5quwkNKPkf181GZ… slot 468,771,102
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-13 03:10:57 UTC Slot 468,771,102, 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 | 51 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-11-13 03:54:10 UTC +43m 13s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-11-13 03:54:10 UTC +43m 13s
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 3 launches from 3 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 4 launches from 4 creator wallets, including this one. See this ticker's page → |
| This document | The same launch document, byte for byte, as 2 other launches, across 3 creator wallets in all. Across the archive, 33.4% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 2 other creator wallets, across 3 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
| Liquidity | 1.9 SOL |
| Read from chain | 2026-11-15 02:58 UTC, just now |
What this launch claimed to be
| Name | Mike Nihaoson |
| Description | Everybody hath a plan until they get punthed in the fath. |
| Metadata held | sha256 4e693b69031182c9399f0aa9eae6838fe5bfc084a097f7abe33abd01725b37d4 · 409 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 be6efd035ec1387cefd4407956c67851c68866eb08b55d969b0e1343c2ffd87e · 179,664 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-13 03:10 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.