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. Public functions allow the 'Minter' owner to add, remove, and update 'SalePhase' objects within a 'Minter', defining different sale configurations. The 'mint' entry function enables users to mint NFTs from a 'Minter' object, requiring payment in SUI and verifying against the active 'SalePhase' and a Merkle proof if applicable. The 'Minter' object tracks total minted NFTs, per-user buys, and per-sale phase buys using dynamic fields (Tables). The 'mint' function mutates the 'Minter' object's minted count and user/phase buy records, and transfers SUI to the 'Minter' owner.
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` configurations within a `Minter` object, controlling minting parameters like price, maximum sales, and per-user mint limits. The `mint` function allows users to mint NFTs, which involves payment in SUI, checks against the current sale phase's rules (including time-gating and an optional Merkle root for allowlist verification), and updates the `Minter`'s `minted` count and user/phase-specific buy counts. Notable patterns include owner-gating for `add_phase`, `remove_phase`, and `update_phase` functions, and time-gating for minting based on `SalePhase.start_time`. The `mint` function also incorporates an optional Merkle tree verification (`verify`, `processProof`, `hash
This 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 `init` function initializes a `Display` object for `Nft`s. The `add_phase`, `remove_phase`, and `update_phase` functions (entry functions) allow the `Minter`'s owner to manage different sale phases, including price, maximum sales, mints per user, start time, and an optional Merkle root for allowlisting. The `mint` entry function allows users to mint NFTs, checking against the current sale phase's rules, including price, supply limits, user-specific mint limits, and Merkle proof verification if an allowlist is active. The `Minter` object's `minted` and `user_buys` fields are mutated during minting, and a new `Nft` object is created and transferred to the minter.
This Sui package defines a Minter object that manages the creation and distribution of Nft objects. The Minter object contains details about the NFT collection, including its name, description, and supply, and it manages a vector of SalePhase objects, each defining a distinct sale period with specific pricing, maximum sales, mints per user, start time, and an optional Merkle root for allowlist gating. Public functions allow the Minter owner to add, remove, and update these sale phases, ensuring that only the owner can modify the sale configuration. The core mint function enables users to mint NFTs by paying a specified SUI amount, verifying against the active sale phase's rules (including time-gating, mints per user, and an optional Merkle proof for allowlisting), and updating the Minter's internal state to track minted NFTs and user purchases. Minted NFTs are transferred to the minter, and the SUI payment is transferred to the Minter's owner.
This package manages Nft objects, which represent digital collectibles with attributes like group_id, type, name, index, description, media_url, and a map of custom attributes. The `init` function creates a Manager object, a Display object for Nfts, and a TransferPolicy for Nfts, sharing all three objects. The TransferPolicy includes a kiosk lock rule and a royalty rule of 600 basis points (6%). Public entry functions allow the package publisher to withdraw SUI from the Manager's balance and to withdraw reserved Nfts from the Manager's dynamic fields into a Kiosk. Users can mint Nfts through the `mint_nft` function, which integrates with a `tradeport_launchpad` module for metadata and payment processing, and can reserve Nfts by adding them to the Manager's dynamic fields. Nft metadata can be added and updated by the publisher, with updates occurring on Nfts locked in a Kiosk.
True specific-lot profit from 211 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).
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
flippernft_traderRule-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": "0xeb61bc2ed35a54e45e7afe8b09af8d78a309cb17929dde11b9723803a5351414",
"n_tx": 1553,
"n_successful_tx": 1530,
"n_distinct_epochs": 291,
"n_distinct_sponsors": 3,
"first_seen_cp": 1577190,
"last_seen_cp": 283223529,
"first_seen_ts_ms": 1683126058946,
"last_seen_ts_ms": 1780616743749,
"total_gas_spent_mist": 11871897974,
"n_self_sponsored_tx": 1536,
"n_sponsored_tx": 17,
"gas_price_p50": 750,
"gas_price_p95": 887,
"active_hours_top24": [
0,
15,
8,
13,
1,
9,
10,
2,
14,
12,
6,
23,
7,
5,
4,
11,
3,
22,
17,
16,
18,
20,
21,
19
],
"primary_archetype": "flipper",
"labels": [
"flipper",
"nft_trader"
],
"label_confidence": [
0.95,
0.9
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).
area + brightness = call volume; hover for detail