all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
counterparties · funders · clusters
Move packages this wallet published on-chain — what it shipped, not what it used.
This Sui package, my_minter, facilitates the creation and management of NFT collections and their associated minting processes. It primarily manages Minter objects, which represent an NFT collection's minting configuration, and Nft objects, which are the individual NFTs. The init function initializes the package, creating a Publisher object for the package, a Display object for Nft, and a CreatorCapability object, all of which are transferred to the deployer. The public/entry functions allow the owner of a Minter object to add, remove, and update SalePhase configurations, which dictate minting parameters like price, maximum sales, mints per user, start time, and an optional Merkle root for allowlisting. The mint function allows users to mint NFTs from a Minter object, checking against the current active sale phase, payment, and optional Merkle proof for allowlisting. It mutates the Minter object by updating minted counts and user buy records, and creates new Nft objects. Notable patterns include owner-gating for administrative
This package defines a new fungible token called SUISAGE. The primary object types it manages are `CoinMetadata<SUISAGE>` and `TreasuryCap<SUISAGE>`. The `init` function is an entry function that creates the SUISAGE currency, setting its name, symbol, description, and icon URL. It then freezes the `CoinMetadata` object and transfers the `TreasuryCap` to the transaction sender, allowing them to mint new SUISAGE tokens. The module uses standard Sui coin creation patterns and transfers the `TreasuryCap` to the deployer.
This package defines a system for managing and minting NFTs within a collection. The primary object types are `Collection`, which represents an NFT collection, `Minter`, which manages the minting process for a specific collection, and `Nft`, which is the actual NFT object. The `init` function initializes the package by creating a `Publisher` and a `Display<Nft>` object, transferring them to the transaction sender. The `add_phase`, `remove_phase`, and `update_phase` entry functions allow the `Minter`'s owner to manage `SalePhase` objects, which define different minting stages with specific prices, limits, and start times. These functions mutate the `phases` vector within the `Minter` object. The `mint` entry function allows users to mint NFTs. It checks the current time against the `SalePhase` start times, verifies merkle proofs if a root hash is present in the `SalePhase`, and updates user-specific and phase-specific buy counts stored in `Table` dynamic fields within the `Minter`
This package defines a custom fungible token called ZOMBIE. The `init` function creates the ZOMBIE currency, freezes its metadata, and transfers the `TreasuryCap<ZOMBIE>` to the deployer. The `mint` entry function allows the holder of the `TreasuryCap<ZOMBIE>` to create new ZOMBIE coins and transfer them to a specified address. The `burn` entry function allows the holder of the `TreasuryCap<ZOMBIE>` to destroy ZOMBIE coins. The package utilizes the standard Sui `coin` module for currency management. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, or royalties.
This Sui package, `pussy_success`, primarily manages a custom fungible token named `PUSSY_SUCCESS`. The `init` function, which is called once upon package deployment, creates the `PUSSY_SUCCESS` currency. It mints a large initial supply (10^19 units) of this token and transfers it to the deployer's address. It also transfers the `TreasuryCap` object to a specific hardcoded address (0x27eb...) and shares the `CoinMetadata` object publicly. The package does not contain any other public or entry functions, meaning users cannot interact with the token beyond its initial creation and distribution. The `PUSSY_SUCCESS` struct itself is a dummy type with a `drop` ability, indicating it's not meant to be stored as a standalone object. The package uses a base64 encoded JPEG image as part of the currency's metadata.
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
Wallets that share a funder, were co-funded by the same personal-scale source, or land in the same behavioral cluster. A heuristic, not proof of common control.
Tinted amber on the bubble map when they appear in the expanded graph.
flippernft_traderRule-based labels, conservative precision.
Where this wallet's SUI first came from, and what it seeded downstream. Observational: a CEX funder suggests a real/retail origin; a high-fanout non-CEX funder is a signal worth noting — not proof of anything.
{
"wallet": "0x6f395e81400132fcdb6c7d6132215e80781ff53eb024c18ed4e38faa09eac48d",
"n_tx": 597,
"n_successful_tx": 587,
"n_distinct_epochs": 66,
"n_distinct_sponsors": 2,
"first_seen_cp": 128873348,
"last_seen_cp": 222070638,
"first_seen_ts_ms": 1743460545016,
"last_seen_ts_ms": 1765500374698,
"total_gas_spent_mist": 5190988376,
"n_self_sponsored_tx": 595,
"n_sponsored_tx": 2,
"gas_price_p50": 550,
"gas_price_p95": 750,
"active_hours_top24": [
1,
2,
12,
17,
13,
0,
11,
16,
20,
4,
23,
19,
22,
15,
14,
21,
3,
18,
10
],
"primary_archetype": "flipper",
"labels": [
"flipper",
"nft_trader"
],
"label_confidence": [
0.95,
0.9
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).
area + brightness = call volume; hover for detail