PHILCATE
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.
noteThe creator sold while we were watching.
noteOnly 1.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-23 23:21 UTC |
| Creator | 6xkYGmNWWjABgfiRGYX3nu54QqteKb6h1CHQNZJv8vkQ |
| Creator took | 1.7% of supply in the first block |
| Outside buyers | 342 distinct wallets, not counting the creator, bought on the bonding curve: 37 within the first 30s, 3 bundled into the creation block. |
| Graduated | 16 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 | 91e79RYKkngGd1yoz2eArp… slot 449,850,733
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-23 23:21:18 UTC Slot 449,850,733, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 37 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-23 23:36:50 UTC +15m 32s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-23 23:36:50 UTC +15m 32s
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 | No other launch we hold a picture for used this one. |
| This ticker | On 2 launches from 1 creator wallet, including this one. See them → |
Pool
| Liquidity | 1.5 SOL |
| Read from chain | 2026-09-25 04:13 UTC, just now |
What this launch claimed to be
| Name | Philcate |
| Description | oui madame |
| Metadata held | sha256 133a287ef1f6c8d127459e44d72d6c27e30392911529df3698d13455a32506e6 · 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-24 23:21 UTC. |
| Picture held | sha256 451f746eed4c2e02be5a97dc03e58f4c7093847955700c6766ad05e272215cf0 · 2,665,252 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-23 23:21 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.