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 within a collection. The primary object types are `Minter`, which represents the NFT collection's configuration, and `Nft`, which is the actual NFT. The `Minter` object stores details like the collection's name, description, owner, total supply, and a vector of `SalePhase` objects. `SalePhase` objects define different sales periods with specific prices, maximum sales, mints per user, and an optional Merkle root for allowlist gating. Public functions allow the `Minter`'s owner to add, remove, and update `SalePhase` configurations. The `mint` function allows users to purchase NFTs, checking against the current sale phase's price, supply limits, and Merkle proof if an allowlist is active. The `mint` function mutates the `Minter` object by updating the `minted` count, user-specific buy counts, and sale phase buy counts, and it creates a new `Nft` object. Notable patterns include time-gating
This Sui package, `my_minter`, primarily manages `Minter` objects, which represent NFT collections, and `Nft` objects, which are the individual NFTs. The `init` function sets up a `Display<Nft>` object for the `Nft` type, transferring both the `Publisher` and `Display` objects 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 minting parameters like 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 from a `Minter`. It checks the current time against sale phases, verifies Merkle proofs if a root is set for the active phase, and enforces `max_sales` and `mints_per_user` limits. It also handles payment by taking a `Coin<SUI>`, mints a
This Sui package defines a Minter object that manages NFT collections and their associated minting phases. The primary objects are Minter, Collection, and Nft. The init function initializes a Display object for Nft and transfers it and a Publisher object to the transaction sender. Public entry functions allow the Minter's owner to add, remove, and update SalePhase objects within a Minter. These functions mutate the Minter's phases vector. The mint function allows users to mint NFTs if they meet the criteria of the active sale phase, which can include price, max sales, mints per user, and a Merkle root for allowlist gating. It mutates the Minter's minted count, user_buys, and sale_phase_buys tables, and transfers a newly created Nft object to the minter. Notable patterns include: owner-gating for phase management functions, time-gating for minting phases, Merkle tree allowlist gating (via the root field in SalePhase), and the use of dynamic fields (Table) to
This package defines a system for managing NFT collections and their minting processes. It primarily manages 'Minter' objects, which represent an NFT collection's minting configuration, and 'Nft' objects, which are the actual NFTs. The 'init' function initializes a 'Publisher' and a 'Display<Nft>' object, transferring both to the transaction sender. Public functions include 'add_phase', 'remove_phase', and 'update_phase', all of which are gated by the 'Minter' object's 'owner' field, allowing only the owner to modify the 'phases' vector within a 'Minter' object. These phases define different sale configurations (price, max sales, mints per user, start time, and an optional Merkle root for allowlisting). The 'mint' function allows users to mint NFTs. It checks the current time against the sale phases, verifies Merkle proofs if a root is provided for the active phase, and updates the 'minted' count in the 'Minter' object and user-specific buy counts in dynamic
True specific-lot profit from 95 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).
1 self-dealing round-trip excluded from the headline (gross incl. wash: $16).
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
flipperRule-based labels, conservative precision.
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": "0x51863aecad09662425401454b313d5538b1e3874b789b2e565e66b72a2dfaad2",
"n_tx": 488,
"n_successful_tx": 477,
"n_distinct_epochs": 32,
"n_distinct_sponsors": 0,
"first_seen_cp": 1588399,
"last_seen_cp": 36980573,
"first_seen_ts_ms": 1683137612459,
"last_seen_ts_ms": 1718643366700,
"total_gas_spent_mist": 2875984276,
"n_self_sponsored_tx": 488,
"n_sponsored_tx": 0,
"gas_price_p50": 885,
"gas_price_p95": 1000,
"active_hours_top24": [
17,
13,
15,
14,
12,
18,
22,
11,
2,
16,
10,
20,
21,
23,
19,
0,
1
],
"primary_archetype": "flipper",
"labels": [
"flipper"
],
"label_confidence": [
0.95
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely UK / W. Europe / W. Africa.
area + brightness = call volume; hover for detail