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 package defines a system for managing and minting NFTs. The primary object types are `Collection` (representing an NFT collection), `Minter` (controlling the minting process for a collection), and `Nft` (the individual NFT). The `init` function initializes the package by creating a `Publisher` and a `Display<Nft>` object, which are then transferred to the transaction sender. The `add_phase`, `remove_phase`, and `update_phase` entry functions allow the `Minter`'s owner to manage `SalePhase` objects within a `Minter`. These phases define different minting conditions (price, max sales, mints per user, start time, and an optional Merkle root for allowlisting). The core `mint` entry function allows users to mint NFTs. It checks the current `SalePhase` based on the current timestamp, verifies Merkle proof if a root is present in the phase, and enforces `max_sales` and `mints_per_user` limits. It also handles payment for the NFT
This Sui package defines a minter for NFTs, centered around the Minter object, which manages the minting process for a specific Collection. The Minter object stores details like the collection ID, owner, supply, and a vector of SalePhase objects, each defining a distinct minting period with its own price, maximum sales, mints per user, start time, and an optional Merkle root for allowlist gating. Public/entry functions allow the Minter's owner to add, remove, and update these SalePhase objects, ensuring only the owner can modify the minting schedule and parameters. The core 'mint' function handles the actual NFT creation, verifying the current time against sale phases, checking user-specific and overall sale limits, and potentially validating a Merkle proof if an allowlist is active for the current phase. Upon successful minting, it transfers the payment, updates the Minter's minted count, and creates a new Nft object, transferring it to the buyer.
This package defines a new fungible token called "MMeow" (MeowMeowCoin). The `init` function, which runs once during package deployment, creates the currency, sets its metadata (name, symbol, description, icon URL), and then freezes the `CoinMetadata` object. It also transfers the `TreasuryCap` object, which controls the minting and burning of MMeow tokens, to the deployer's address. The primary object type managed is `CoinMetadata<MMEOW>` and `TreasuryCap<MMEOW>`. The package utilizes the `coin` and `transfer` modules for token creation and ownership transfer.
This package, my_minter, primarily manages two object types: Minter and Nft. The Minter object represents a collection's minting configuration, holding details like the collection's name, description, owner, total supply, minted count, and a vector of SalePhase objects. Each SalePhase defines a specific minting period with its price, maximum sales, mints per user, start time, name, and an optional Merkle root for allowlist gating. The Nft object represents an individual NFT, storing its ID, name, description, image URLs, collection ID, symbol, attributes, and creator. The public/entry functions allow the Minter's owner to manage sale phases and for users to mint NFTs. add_phase, remove_phase, and update_phase enable the Minter's owner to add, remove, or modify SalePhase entries within the Minter object, respectively. The mint function allows users to mint NFTs, checking against the active SalePhase's start time, price, maximum sales, and mints per user. It
This package defines a system for managing NFT collections and minting. It primarily manages Collection objects, which represent an NFT collection, and Minter objects, which control the minting process for a specific collection. The Nft object represents an individual NFT. The init function initializes the package by claiming the Publisher capability and creating a Display object for Nft, transferring both to the transaction sender. Public/entry functions: add_phase: Allows the Minter's owner to add a new SalePhase to the Minter object, defining minting parameters like price, max sales, mints per user, start time, and an optional Merkle root for allowlisting. This mutates the Minter object. remove_phase: Allows the Minter's owner to remove an existing SalePhase from the Minter object based on its name. This mutates the Minter object. update_phase: Allows the Minter's owner to modify an existing SalePhase within the Minter object. This mutates the Minter object. mint: Allows users to mint NFTs
True specific-lot profit from 5 closed buy→sell round-trips of the same NFT (realized_roundtrip), wash-adjusted, valued at each leg's trade-hour USD. Excludes still-held inventory (that's unrealized).
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
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": "0x3d9c7b9e591ed2cf1367870c0226d66db6f34b3a5c649d195cd5839af33d3c4b",
"n_tx": 599,
"n_successful_tx": 587,
"n_distinct_epochs": 118,
"n_distinct_sponsors": 2,
"first_seen_cp": 1655217,
"last_seen_cp": 198131236,
"first_seen_ts_ms": 1683206403123,
"last_seen_ts_ms": 1759838728366,
"total_gas_spent_mist": 2294523840,
"n_self_sponsored_tx": 594,
"n_sponsored_tx": 5,
"gas_price_p50": 750,
"gas_price_p95": 755,
"active_hours_top24": [
15,
9,
20,
16,
13,
7,
8,
14,
10,
22,
18,
11,
12,
17,
21,
23,
19,
6,
5
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely C. Europe / Africa / Middle East.
area + brightness = call volume; hover for detail