HostDeFi › Deployers › 3fxy…i32S

Deployer 3fxy…i32S

Tallied from HostDeFi's own launch captures · 2026-09-07 → 2026-09-15 · a ledger record, not an accusation or endorsement

3fxyiYoWtZkZC6jR4FKUznnLkGK7C2APMowEFXzdi32S

Launches on ledger

642

First seen

2026-09-07

Last seen

2026-09-15

Biggest capture mcap

$13.60K

Venue split on the ledger: pump ×491 · unstamped ×151.

The deployer record

Deployer 3fxyiYoWtZkZC6jR4FKUznnLkGK7C2APMowEFXzdi32S minted 642 tokens across four days between September 7 and September 15, 2026 — 175 on debut, a 412 peak on the 8th, then a five-day gap and a small tail of 18 and 37.

Its two captured pool rows are the same name twice — "Porsche", minted as two separate tokens — the name-looper pattern: identical tickers re-issued as distinct mints, where only the deployer field connects the siblings. Neither graduated.

The shape is a classic two-day burst plus a restart a week later: a batch run, silence, then a smaller second batch. At 412 launches on its peak day the wallet was producing roughly seventeen an hour.

For a reader, the practical fact is the count and the repetition: a "Porsche" whose deployer field shows this address is one of at least two identically-named tokens from one wallet's six-hundred-launch run. The dev-wallet guide puts cadence first, and the launch statistics place a four-hundred-day burst against the feed. Tallies are dated to the September 7–15 window; the ledger keeps counting.

HostDeFi is an educational risk tool, not financial advice. Deployer records tally our own dated launch captures; the ledger observes a sample, not the wallet's whole history, and presence here is neither listing nor accusation. How this page was made: the tallies are counted from HostDeFi's own launch captures at render time, and the written record is the HostDeFi desk's own write-up of this one wallet, dated to the window it describes. A HostDeFi product