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 minter for NFTs, centered around the Minter object. It allows for the creation and management of NFT collections with configurable sale phases. Public functions enable the owner to add, remove, and update sale phases, each having a price, maximum sales, mints per user, start time, name, and an optional Merkle root for allowlist gating. The core mint function handles the purchase of NFTs, verifying the active sale phase, checking against supply limits and user-specific mint limits, and optionally validating a Merkle proof. Minting involves transferring SUI, updating internal counters for total minted and per-phase/per-user buys, and emitting an NFTMinted event.
This Sui package, `my_minter`, primarily manages `Minter` and `Nft` objects. The `Minter` object acts as a central configuration for an NFT collection, holding details like the collection's name, description, total supply, and a vector of `SalePhase` objects. Each `SalePhase` defines a specific sale period with its own price, maximum sales, mints per user, start time, name, and an optional Merkle root for allowlist gating. The `Nft` object represents an individual NFT with its metadata. The public/entry functions allow for the management of sale phases and the minting of NFTs. `add_phase`, `remove_phase`, and `update_phase` are administrative functions that allow the `Minter`'s owner to modify the sale phases within a `Minter` object. These functions mutate the `phases` vector of the `Minter`. The `mint` function allows users to purchase NFTs. It checks the current time against sale phase start times, verifies Merkle proofs if an allowlist
This Sui package defines a minter for NFTs. It manages Collection objects, which represent NFT collections, and Minter objects, which control the minting process for a specific collection. The primary object type is Nft, which stores metadata like name, description, image URL, and attributes. The public/entry functions allow the Minter's owner to add, remove, and update sale phases, each with a price, max sales, mints per user, start time, and an optional Merkle root for allowlisting. The mint function allows users to mint NFTs by paying SUI, checking against sale phase rules (time-gating, max sales, mints per user, and Merkle proof verification if a root is provided). It mutates the Minter object by updating minted counts and user buy counts, and creates new Nft objects. Notable patterns include: admin caps (only the Minter owner can modify sale phases), time-gating (minting is restricted by sale phase start times), and allowlist gating (using Merkle proofs for specific sale phases).
casualRule-based labels, conservative precision.
area + brightness = call volume; hover for detail
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": "0x28f51ea995d2884755f81ec570c1c6d152b3985247144d5bf7f5d65571faf652",
"n_tx": 28,
"n_successful_tx": 26,
"n_distinct_epochs": 6,
"n_distinct_sponsors": 0,
"first_seen_cp": 1659948,
"last_seen_cp": 13205486,
"first_seen_ts_ms": 1683211279275,
"last_seen_ts_ms": 1694951241099,
"total_gas_spent_mist": 338654612,
"n_self_sponsored_tx": 28,
"n_sponsored_tx": 0,
"gas_price_p50": 1000,
"gas_price_p95": 1000,
"active_hours_top24": [
18,
11,
13,
14,
15,
19
],
"primary_archetype": "casual",
"labels": [
"casual"
],
"label_confidence": [
0.7
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely UK / W. Europe / W. Africa.