5.1%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
205launches carry this ticker, from 147 creator walletsNo finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.
Also recorded, and not part of the finding above: this creator has 25 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.
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.
noteThe creator sold while we were watching.
At launch
| Created | 2026-09-10 12:05 UTC |
| Creator | 29WnaRv6eoJUCpuUVfLexTefZLE1QU9HT5PMLZh4qBWs |
| Creator took | 5.1% of supply in the first block |
| Outside buyers | unknown 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: 74 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 | yes; we did not record when |
| Curve on chain | Complete. We read the bonding curve account 62.6 days ago and it was finished. Checked 2026-09-10 15:01 UTC. |
| Creator sold | yes |
| Recorded from | 66J3joSs8b2Nr4wLHxigqW… slot 445,879,787
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Order of events
| Created | 2026-09-10 12:05:30 UTC Slot 445,879,787, 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 | 74 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-09-10 13:26:17 UTC +1h 20m 47s
4.109e-7 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
| Curve completed | Recorded as complete; we did not record when.
Confirmed against the venue's own completion state. |
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 205 launches from 147 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.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| This creator | 25 earlier launches, none of which reached a graduation threshold while we watched. Across the archive, 70.6% 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 9 other creator wallets, across 13 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.9% 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 | FEET COIN |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 ff93bfe355f2092b3215bd651a56a9ac1422e54ad36d34f7a251b147d9fbe2f7 · 395 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 | The address no longer served it when re-read 2026-09-17 14:07 UTC. The launch-time capture above is the surviving record. |
| Picture held | sha256 d6c34e0d562186e6f7cee3f879d5b3af2f8ba6ff06e8f9f9e492f1eb8a20f7b6 · 10,822 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 12:05 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.