FILLED
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 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 16:10 UTC |
| Creator | 2vC3cxpbqGuVpjVVY8UGk3XxkJfuEZHBFgD1xXrszmLJ |
| Creator took | 0.6% of supply in the first block |
| Outside buyers | 229 distinct wallets, not counting the creator, bought on the bonding curve: 53 within the first 30s, 2 bundled into the creation block. |
| Graduated | 14 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 | 2gVhwr6ut4BZMcHiksTFK7… slot 452,660,049
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:10:11 UTC Slot 452,660,049, 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. |
| Highest price seen | 2026-10-02 16:10:11 UTC
0.000e+0 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. |
| Thirty seconds in | 53 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 16:24:19 UTC +14m 08s Confirmed: a PumpSwap pool was found for it. |
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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 20 launches from 19 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 2 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 | 0.0 SOL |
| Read from chain | 2026-10-02 20:07 UTC, just now |
What this launch claimed to be
| Name | filled.cards |
| Description | Limit orders and terminal for Cards Powered by @Collector_Crypt |
| Metadata held | sha256 52c316c2de1b7369e0c85b1a5ff3560b39c0d0e08f7a74cffefe708aecc7ff5d · 436 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 8940f2506f576db1633e47264a483d01aa20660785e561d098707fa3cb3b7d9b · 203,666 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 16:10 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.