MEE
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 16:30 UTC |
| Creator | 94XsRe3BjvfJ74EzqRWMRyx9LGKz1KEKrvU2jDDdGcce |
| Creator took | 0.3% of supply in the first block |
| Outside buyers | 21 distinct wallets, not counting the creator, bought on the bonding curve: 10 within the first 30s, 0 bundled into the creation block. |
| Graduated | 1.0 h 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 | 5oNqjTqQ1Nx7sBzbE5vZP5… slot 452,664,693
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 16:30:53 UTC Slot 452,664,693, 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 | 10 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-10-02 17:31:42 UTC +1h 00m 50s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 17:31:42 UTC +1h 00m 50s
0.000e+0 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. |
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 10 launches from 8 creator wallets, including this one. See them → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-02 20:46 UTC, just now |
What this launch claimed to be
| Name | ITSMEE |
| Description | ItsMee Memecoin - No Utility - Made by BTC OG |
| Metadata held | sha256 6d841f7e2faa4ff09ec011382a5421d118339dd0c012b6db4c64b3f13d38da59 · 270 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 9ad0b5509fa75b336bf8d7743b477d966fe2b2f42ac9a734f6ca7d83451486e3 · 87,137 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 16:31 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.