all collections · daily · marketplace overlay
weekly · real (teal) vs wash (rose)
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. It primarily manages `Minter` objects, which represent an NFT collection and its associated minting rules, and `Nft` objects, which are the individual NFTs. The `init` function initializes the package by creating a `Publisher` object, a `Display<Nft>` object for metadata, and a `CreatorCapability` object, transferring them to the sender. Public functions allow the owner of a `Minter` object to `add_phase`, `remove_phase`, and `update_phase` for the NFT collection, which modify the `phases` vector within the `Minter` object. These phases define different sale conditions like price, max sales, mints per user, start time, and an optional Merkle root for allowlisting. The `mint` function allows users to mint NFTs, checking against the active sale phase, Merkle proof (if provided), and user-specific mint limits. It mutates the `Minter` object's `minted` count, `user_buys
The package manages three primary object types: Collection, Minter, and Nft. The `init` function creates a `CreatorCapability` object and transfers it to the sender, along with a `Publisher` and `Display<Nft>` object. The `add_phase`, `remove_phase`, and `update_phase` entry functions allow the `Minter`'s owner to manage sale phases, which include price, max sales, mints per user, start time, and an optional Merkle root for allowlist gating. The `mint` entry function allows users to mint NFTs, checking for time-gating, Merkle proof verification (if a root is present), and per-user/per-phase mint limits. It also handles payment and transfers the newly minted NFT to the sender. The `CreatorCapability` acts as an admin cap for managing the minter's sale phases.
This package, my_minter, primarily manages Minter objects, which represent NFT collections, and Nft objects, which are the individual NFTs. Public functions allow the Minter's owner to add, remove, and update sale phases, which are time-gated and can have allowlists (Merkle roots) and limits on total sales or mints per user. The mint function allows users to purchase NFTs, checking against the active sale phase's price, supply, and user limits, and verifies Merkle proofs if an allowlist is active. It mutates the Minter's minted count and user_buys/sale_phase_buys tables, and transfers the minted Nft to the sender. The package also includes helper functions for Merkle tree verification and string conversions.
This package defines a system for managing NFT collections and minting. The primary object types are `Collection` (representing an NFT collection), `Minter` (managing the minting process for a collection), and `Nft` (the individual NFT). The `init` function creates a `Publisher` and a `Display` object for `Nft`s, transferring both to the sender, and also transfers a `CreatorCapability` to the sender. This `CreatorCapability` is likely used for administrative actions. Public/entry functions allow the `Minter` owner to `add_phase`, `remove_phase`, and `update_phase` for the minting process, which define different sale phases with specific pricing, maximum sales, mints per user, start times, and optional Merkle roots for allowlisting. The `mint` function allows users to mint NFTs, checking against the current active sale phase, price, and Merkle root (if applicable), and updates the `minted` count and user/phase buy counts within the `Minter` object. Notable
{
"wallet": "0x2e11042563a6d6a26eb3eff2ec42233ca9cddaca3ac55197a575cb3f812fc7f6",
"n_tx": 114,
"n_successful_tx": 113,
"n_distinct_epochs": 22,
"n_distinct_sponsors": 0,
"first_seen_cp": 65624353,
"last_seen_cp": 128027743,
"first_seen_ts_ms": 1728117063444,
"last_seen_ts_ms": 1743261101832,
"total_gas_spent_mist": 963954296,
"n_self_sponsored_tx": 114,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
9,
15,
14,
7,
11,
6,
4,
12,
2,
8,
13,
17,
3,
1,
16
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W/Central Asia / India.
area + brightness = call volume; hover for detail