ONCHAIN
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
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.
noteOnly 2.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 08:04 UTC |
| Creator | ETVicks3BkRNUZTJvBKvw6swn8b6rbCiEFWXox96fGC3 |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 149 distinct wallets, not counting the creator, bought on the bonding curve: 0 within the first 30s, 0 bundled into the creation block. |
| Graduated | 2 min after launch |
| Curve, read 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 | not while we watched |
| Recorded from | 2TAZyywNQehHLFATTWvixi… slot 452,550,765
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 08:04:03 UTC Slot 452,550,765, 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 | No buyer, 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-10-02 08:05:34 UTC +1m 31s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 08:05:34 UTC +1m 31s
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 4 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 66 launches from 63 creator wallets, including this one. See them → |
| This document | Byte-identical to 4 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 4 other creator wallets, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 5 creator wallets. See the linked wallets → |
Pool
| Liquidity | 2.7 SOL |
| Read from chain | 2026-10-02 14:44 UTC, just now |
What this launch claimed to be
| Name | Ape On Chain |
| Description | Many bonders, Many more overlooked.. |
| Metadata held | sha256 1052fd0c12136d9c82f8383fe9cc985d29940976fbcdfcf1730690123d474b0f · 295 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 a08ad93475bcda7d55be10a8d56a6d062b75d1da80727180260cf639ab54cfa8 · 2,200,600 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 08:04 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.