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`, primarily manages `Minter` and `Nft` objects. The `Minter` object represents a collection's minting configuration, including its owner, supply, and a vector of `SalePhase` objects, which define different minting stages with specific prices, maximum sales, mints per user, start times, and optional Merkle roots for allowlisting. The `Nft` object represents a non-fungible token with properties like name, description, image URL, and creator. Public/entry functions allow the `Minter`'s owner to `add_phase`, `remove_phase`, and `update_phase` to manage the minting phases. The `mint` function allows users to mint NFTs by paying a specified SUI amount, with checks for current time, available supply, and per-user mint limits. If a Merkle root is present in the active `SalePhase`, the `mint` function also performs a Merkle proof verification using the `verify` function. The `mint` function mutates
This Sui package, `my_minter`, primarily manages `Minter` and `Nft` objects. The `init` function initializes a `Publisher` and `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 within the `Minter`, which define sale parameters like price, max sales, and start time. The `mint` function allows users to mint `Nft` objects, requiring payment and checking against the active `SalePhase` for price, supply limits, and user-specific mint limits. The `mint` function also includes a Merkle tree verification logic (`processProof`, `verify`) for potential allowlist gating, although its usage is not fully shown.
This Sui package defines a minter for NFTs, primarily managing Minter and Nft objects. The Minter object holds details about the NFT collection, including its owner, supply, and a vector of SalePhase objects, which define different sale configurations (price, max sales, mints per user, start time, and an optional Merkle root for allowlisting). It also tracks user and sale phase specific mint counts using tables. Public/entry functions allow the Minter's owner to add, remove, and update sale phases, ensuring only the owner can modify these configurations. The core 'mint' function enables users to mint NFTs. This function checks the current active sale phase based on the current timestamp, verifies Merkle proofs if an allowlist is active for that phase, and enforces per-user and overall sale limits. It also handles payment by taking a Coin<SUI> and transferring it to the minter's owner. Notable patterns include: owner-based access control for managing sale phases, time-gating for sale phases, optional Merkle tree allowlisting for
This package defines a system for managing NFT collections and their minting processes. It primarily manages 'Minter' objects, which represent an NFT collection and its associated minting rules, and 'Nft' objects, which are the individual NFTs. Public functions allow the 'Minter' owner to add, remove, and update 'SalePhase' objects within a 'Minter'. These 'SalePhase' objects define different minting periods with specific prices, maximum sales, mints per user, and an optional Merkle root for allowlist gating. The 'mint' function allows users to mint NFTs, checking against the active 'SalePhase' for price, supply, user limits, and an optional Merkle proof. Notable patterns include: admin caps (only the 'Minter' owner can modify sale phases), time-gating (sale phases have start times), allowlist gating (optional Merkle root in 'SalePhase'), and dynamic fields (using 'Table' for 'user_buys' and 'sale_phase_buys'). The 'init' function initializes a '
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections, and `Nft` objects, which are the individual NFTs. Public/entry functions allow the `Minter`'s owner to add, remove, and update `SalePhase` objects within a `Minter`. These functions mutate the `phases` vector of the `Minter` object. The `mint` function allows users to mint NFTs from a `Minter` object, transferring SUI in exchange. This function mutates the `Minter`'s `minted` count, `user_buys` table, and `sale_phase_buys` table, and creates new `Nft` objects. Notable patterns include owner-gating for `add_phase`, `remove_phase`, and `update_phase` functions, ensuring only the `Minter`'s owner can modify sale phases. The `mint` function incorporates time-gating based on `SalePhase` start times and utilizes a Merkle tree verification process (`
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.
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": "0x9a2e12fd4fcb2206f37c6878cf834a568f1fe04cf35a20939b850502499212cd",
"n_tx": 79,
"n_successful_tx": 79,
"n_distinct_epochs": 10,
"n_distinct_sponsors": 0,
"first_seen_cp": 2564791,
"last_seen_cp": 6964491,
"first_seen_ts_ms": 1684164069731,
"last_seen_ts_ms": 1688641923758,
"total_gas_spent_mist": 1000475052,
"n_self_sponsored_tx": 79,
"n_sponsored_tx": 0,
"gas_price_p50": 930,
"gas_price_p95": 930,
"active_hours_top24": [
15,
10,
19,
18,
20,
22,
16,
21,
11,
23,
12,
14
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely Atlantic / E. South America.