PAIDCATE
The curve completed in the same batch of events as the 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.
findingOnly 3 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
At launch
| Created | 2026-09-19 17:43 UTC |
| Creator | 4xwXEAAvjfhLgfJnHoMpWYgp5Jo1NrQoNx1Ju22pcrvz |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 3 distinct wallets, not counting the creator, bought on the bonding curve: 3 within the first 30s, 3 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 7.0 h ago and it was finished. Checked 2026-09-19 18:10 UTC. |
| Creator sold | not while we watched |
| Recorded from | 29kysuwe8rD491FinoeuhC… slot 448,478,516
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-19 17:43:56 UTC Slot 448,478,516, 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. |
| Curve completed | 2026-09-19 17:43:56 UTC +0s Confirmed against the venue's own completion state. |
| Thirty seconds in | 3 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. |
| Highest price seen | 2026-09-19 19:02:51 UTC +1h 18m 55s
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 11 launches from 11 creator wallets, including this one. See them → |
Pool
| Liquidity | 78.2 SOL |
| Read from chain | 2026-09-20 01:08 UTC, just now |
What this launch claimed to be
| Name | PAIDCATE |
| Description | paidcate, about to take over cate |
| Metadata held | sha256 6376ed2a3d3dd05c2d43871344b450bc0daa481f3af0fea6a4f2f3e38a0c7dd8 · 227 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 581ce6cfe4390c3e3faf2af51db5dbb3af08d85f21d40e3642e2e546fe774a23 · 1,580,444 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-19 17:43 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.