Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 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.4% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
At launch
| Created | 2026-11-11 18:47 UTC |
| Creator | Er4SmMaiMTSAvK1RSY6i92zm5BpYvaP1h11VZcWFCSrx |
| Creator took | 4.9% of supply in the first block |
| Outside buyers | 387 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: 11 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 4 min after launch |
| Curve on chain | Complete. We read the bonding curve account 1.9 days ago and it was finished. Checked 2026-11-11 19:00 UTC. |
| Creator sold | not while we watched |
| Recorded from | FBudykP6aeVGaxFczSqH4v… slot 468,229,269
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-11 18:47:41 UTC Slot 468,229,269, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 11 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-11 18:51:14 UTC +3m 33s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-11-11 18:51:14 UTC +3m 33s
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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.4% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 360 launches from 297 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 → |
| This document | The same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 33.2% 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 1 other creator wallet, 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 of 2 creator wallets in all. Across the archive, 63.8% 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 | Robo Party Ape |
| Description | Relaunched. Robo party ape in MachiPool now. |
| Metadata held | sha256 46f350119a0e3f40b34bb2a65cf8495a7c8c0a7339c503f32f9ca4196c121b18 · 328 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-12 18:48 UTC. |
| Picture held | sha256 01ad2e911f3634626c519e66c82654c3b8bca232bc64ced9fc2cfa47f8e12269 · 1,418,010 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-11 18:47 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.