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 primarily manages `Nft` objects, which represent non-fungible tokens with fields for ID, name, description, media URL, and attributes (a map of strings to strings). The `init` function initializes the module by creating a `Publisher` object, a `Display` object for `Nft`s with predefined metadata fields, and a `TransferPolicy` for `Nft`s. This `TransferPolicy` includes a `kiosk_lock_rule` and a `royalty_rule` set at 200 basis points (2%). The public entry functions `mint_order`, `mint_nft`, and `mint_edition_nft` all delegate to functions within the `launchpad` module, suggesting this package integrates with a broader NFT launchpad system. The `update_nft` function allows for modifying the name, description, media URL, and attributes of an `Nft` object, requiring a `Manager` object and a `KioskOwnerCap` if the NFT is held in a Kiosk. Notably, the `TransferPolicy` with
This package primarily manages `Nft` objects, which represent non-fungible tokens with fields for name, description, media URL, and dynamic attributes. The `init` function initializes the package by creating a `Display` object for `Nft`s, setting up metadata fields, and establishing a `TransferPolicy` with a Kiosk lock rule and a 100 basis point royalty fee. Public functions include `mint_order`, `mint_nft`, and `mint_edition_nft`, which delegate to a `launchpad` module to facilitate different NFT minting processes, potentially involving payments and kiosk interactions. The `update_nft` function allows for modifying the metadata (name, description, media URL, and attributes) of an existing `Nft` object held within a Kiosk. Notable patterns include the use of a `TransferPolicy` for enforcing rules like royalties and Kiosk locking, and the delegation of core minting logic to an external `launchpad` module.
This package primarily manages an `Nft` object type, which represents a non-fungible token with an ID, name, description, media URL, and dynamic attributes. The `init` function initializes the package by creating a `Publisher` object, a `Display` object for `Nft`s with predefined metadata fields, and a `TransferPolicy
This package manages an Nft object type, representing a "Seal Pioneer" badge with a name, description, media URL, and dynamic attributes. The `init` function initializes the package by creating a Publisher object, a Display object for Nft metadata (setting various display fields like collection name, description, and media URL), and a TransferPolicy for Nft objects. This TransferPolicy is configured with a KioskLockRule and a RoyaltyRule (100 basis points, or 1%). The `mint_order`, `mint_nft`, and `mint_edition_nft` public entry functions delegate to a `launchpad` module to handle the actual minting logic, creating new Nft objects and potentially placing them into a Kiosk. The `update_nft` function allows a Manager to modify the name, description, media URL, and attributes of an existing Nft object, which is borrowed from a Kiosk. The package utilizes dynamic fields for Nft attributes and implements royalties and kiosk locking through the TransferPolicy.
This package primarily manages an `Nft` object type, which represents a non-fungible token with an ID, name, description, media URL, and a map of attributes. The `init` function initializes a `Display` object for `Nft`s, sets up a `TransferPolicy` for `Nft`s that includes a Kiosk lock rule and a 100 basis point royalty rule, and then transfers ownership of the `Publisher`, `Display`, and `TransferPolicyCap` to the transaction sender, while sharing the `TransferPolicy` object. Public functions `mint_order`, `mint_nft`, and `mint_edition_nft` delegate to a `launchpad` module to handle the minting process, creating new `Nft` objects and potentially placing them in a Kiosk. The `update_nft` function allows a `Manager` to modify the name, description, media URL, and attributes of an existing `Nft` object, which is retrieved from a Kiosk. Notable patterns include the use of `Display` for metadata, `TransferPolicy
True specific-lot profit from 14 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).
flipperflipperRule-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": "0x897f4ff87f264d2e62f4ede469de4facee1a220ecffb4fae97ee0a92730ed3ee",
"n_tx": 1817,
"n_successful_tx": 1803,
"n_distinct_epochs": 200,
"n_distinct_sponsors": 0,
"first_seen_cp": 62012489,
"last_seen_cp": 271027463,
"first_seen_ts_ms": 1727237161613,
"last_seen_ts_ms": 1777655098416,
"total_gas_spent_mist": 4264606844,
"n_self_sponsored_tx": 1817,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
18,
20,
5,
16,
4,
2,
8,
0,
14,
17,
9,
6,
12,
22,
3,
10,
13,
1,
21,
15,
19,
23,
11,
7
],
"primary_archetype": "flipper",
"labels": [
"flipper",
"flipper"
],
"label_confidence": [
1,
0.5775
],
"bot_score": 0.3,
"bot_signals": [
"floor_arb_bot"
],
"cex_label": null
}Top active hours by UTC. Flat around the clock → no timezone signal (likely automated).
area + brightness = call volume; hover for detail