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 Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections. It also defines `Nft` objects for the individual NFTs and `SalePhase` objects to configure different sale periods. Public/entry functions allow the `Minter`'s owner to `add_phase`, `remove_phase`, and `update_phase` to manage the sale phases of the NFT collection. These functions mutate the `phases` vector within the `Minter` object. The `mint` function allows users to mint NFTs from the collection, which involves checking sale phase conditions, verifying Merkle proofs if applicable, and transferring SUI. 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 potentially allowlist gating through Merkle proof verification (`root` field in `SalePhase`). It also tracks `m
This package defines a system for managing NFT collections and minting NFTs. It primarily manages 'Minter' objects, which represent an NFT collection and its associated minting logic, and 'Nft' objects, which are the individual NFTs. Public/entry functions allow the owner of a 'Minter' to add, remove, and update 'SalePhase' objects, which define different minting stages with specific prices, maximum sales, and per-user mint limits. The 'mint' function allows users to mint NFTs, checking against the active sale phase, user-specific mint limits, and overall supply. It mutates the 'Minter' object by updating minted counts and user/phase buy records, and creates new 'Nft' objects. Notable patterns include: owner-gating for phase management functions, time-gating for sale phases, and the use of Merkle proofs (via 'processProof' and 'verify' functions) for potential allowlist functionality within sale phases. It also uses dynamic fields (Tables) to track user and sale phase buy counts.
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
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": "0xc12913b63ced6838a4a65e90c775323e434497af4b08c6b261e4c9332fe25f91",
"n_tx": 35,
"n_successful_tx": 35,
"n_distinct_epochs": 9,
"n_distinct_sponsors": 0,
"first_seen_cp": 2490138,
"last_seen_cp": 60753516,
"first_seen_ts_ms": 1684078174409,
"last_seen_ts_ms": 1726933095107,
"total_gas_spent_mist": 239458352,
"n_self_sponsored_tx": 35,
"n_sponsored_tx": 0,
"gas_price_p50": 915,
"gas_price_p95": 931,
"active_hours_top24": [
18,
17,
19,
16,
15,
5,
20,
12,
13
],
"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 Atlantic / E. South America.