BlackHoles
The creator took 27% of supply at 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.
noteThe creator took 26.8% of supply at launch.
At launch
| Created | 2026-10-02 02:09 UTC |
| Creator | AEGuBv8qZTuBiqSYvDhktpk5F1DHUgvdKTxnLh81HaWm |
| Creator took | 26.8% of supply in the first block |
| Outside buyers | 75 distinct wallets, not counting the creator, bought on the bonding curve: 10 within the first 30s, 0 bundled into the creation block. |
| Graduated | 24 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 | 4XA4wZntEbsPWB7sMwb2LV… slot 452,471,361
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 02:09:47 UTC Slot 452,471,361, 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 02:33:29 UTC +23m 42s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 02:33:29 UTC +23m 42s
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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 3 launches from 3 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, 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 | 166.3 SOL |
| Read from chain | 2026-10-02 12:49 UTC, just now |
What this launch claimed to be
| Name | BlackHoles |
| Description | All-in-One Wallet for the Entire Universe |
| Metadata held | sha256 6983b9e2359e77cb92c15b03e904b76e7c1a8f2dfe9b869ef6442906b27d2dcb · 343 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 31094881075034cdfa41d92c100cf3c3062355c367e9ceb894d088e69a62eb8f · 282,945 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 02:09 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.