Blob
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-10-02 15:07 UTC |
| Creator | 3pyxcxefJSg5sTyg92BbxUwRgbxLkXvpKrkhQwc9VYTy |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 1,053 distinct wallets, not counting the creator, bought on the bonding curve: 248 within the first 30s, 22 bundled into the creation block. |
| Graduated | 5 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 6.9 h ago and it was finished. Checked 2026-10-02 15:31 UTC. |
| Creator sold | yes |
| Recorded from | 3TFe3MnN7dapg588szKkFG… slot 452,645,985
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 15:07:28 UTC Slot 452,645,985, which is the chain's own clock for this moment. |
| Creation block | 22 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 248 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 15:12:19 UTC +4m 52s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-02 15:12:22 UTC +4m 54s
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 11 launches from 9 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 133 launches from 85 creator wallets, including this one. See them → |
| This document | Byte-identical to 2 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 6 other creator wallets, across 3 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 | 1.5 SOL |
| Read from chain | 2026-10-02 22:22 UTC, just now |
What this launch claimed to be
| Name | Blobcoin |
| Metadata held | sha256 fb4dc00d1646606e4ad8f259dd4fa40b342c50d4f11b32d87eb198674c9b6ea6 · 415 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 744717aed08ae21e6452244809d5a72054f0514c0fa90a8ce07e1326ab074abb · 17,792 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 15:07 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.