AMOEBA
The creator took 35% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
noteThe creator took 35.5% of supply at launch.
noteThe creator sold while we were watching.
noteOnly 1.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 04:20 UTC |
| Creator | 6XgsWyc6Xz4QPdsTohUb827yDEFg2JjZevSvzuWpCAqX |
| Creator took | 35.5% of supply in the first block |
| Outside buyers | 81 distinct wallets, not counting the creator, bought on the bonding curve: 21 within the first 30s, 2 bundled into the creation block. |
| Graduated | 2 min after launch |
| Curve, read 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 | 2raT5wqbKsAV58i4ThpGTm… slot 451,855,001
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 04:20:14 UTC Slot 451,855,001, which is the chain's own clock for this moment. |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 21 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-09-30 04:22:41 UTC +2m 27s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 04:22:41 UTC +2m 27s
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 71 launches from 6 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 80 launches from 14 creator wallets, including this one. See them → |
| This creator | 61 earlier launches, 4 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 5 other creator wallets, across 10 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 1.0 SOL |
| Read from chain | 2026-10-01 23:04 UTC, just now |
What this launch claimed to be
| Name | AMOEBA |
| Metadata held | sha256 a53138bbc37dc89bf84a8177b1c3c53ea42b2ee4acd90fb4b8ad7fbac912fd32 · 331 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-10-01 04:21 UTC. |
| Picture held | sha256 353663c2bee3147d722d9f0d6f300385624728bb90028551bea6a49c1f7b07ed · 330,895 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 04:20 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.