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 defines a non-fungible token (NFT) called `Nft` with fields for ID, name, description, media URL, and dynamic attributes. The `init` function initializes a `Display` object for the `Nft` type, setting various display properties, and creates a `TransferPolicy` with a Kiosk lock rule and a 2.5% royalty rule, transferring these administrative objects to the deployer. The `create_nft_with_verification` entry function mints a new `Nft` object and associates its ID with a `Verification` object from the `launchpad` module. The `update_nft_with_verification` entry function allows modification of an existing `Nft`'s fields (name, description, media URL, attributes) if the provided `ID` matches the `Verification` object's associated NFT ID, requiring a `Kiosk` and `KioskOwnerCap` to borrow the NFT.
This Sui package, `af_lp`, defines a single dummy struct `AF_LP`. Its primary function, `init`, is called once during package deployment. This `init` function immediately calls `amm_interface::create_lp_coin` with the `AF_LP` object, a constant value of 7, and the transaction context. This suggests that `af_lp` is likely a minimal wrapper module designed to register a new LP (Liquidity Provider) coin type, `AF_LP`, within an existing AMM (Automated Market Maker) system. The module itself does not manage any state beyond this initial registration.
This Sui package manages a primary object type called `Nft`, which represents a non-fungible token with an ID, name, description, media URL, and dynamic attributes stored as a `VecMap`. The `init` function initializes a `Display` object for `Nft` metadata, a `TransferPolicy` with a Kiosk lock rule and a 10% royalty rule (1000 basis points out of 10000), and transfers these administrative objects to the deployer. Public functions `mint_order`, `mint_nft`, and `mint_edition_nft` delegate to a `launchpad` module for NFT minting, suggesting a launchpad integration. The `update_nft` function allows a manager to modify an existing `Nft`'s name, description, media URL, and attributes, retrieving the NFT from a Kiosk for mutation.
This package defines a single primary object type, BAG, which is a dummy struct. The `init` function is the only public/entry function, and it creates a new fungible token (Coin) of type BAG. It initializes the CoinMetadata for BAG with a name, symbol, description, and an IPFS URL for its icon, then transfers both the TreasuryCap and CoinMetadata objects to the transaction sender. This module essentially sets up the basic infrastructure for a new fungible token named "BAG" with specific metadata.
The `af_lp` package defines a dummy `AF_LP` struct. Its single public function, `init`, takes an `AF_LP` object and a `TxContext` as input. This function calls `amm_interface::create_lp_coin` with the provided `AF_LP` object, a constant value of 7, and the transaction context. This suggests the package's primary purpose is to initialize a liquidity pool coin (LP coin) of type `AF_LP` within an Automated Market Maker (AMM) interface, likely representing a specific LP token with a predefined identifier (7). The package itself does not manage any objects directly but rather interacts with the `amm_interface` to create an LP coin.
True specific-lot profit from 40 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: $533).
marketplace NFT sales from analytics.sale. Net = proceeds − spend; realized trading flow, not true PnL (ignores still-held NFTs; wash trades inflate both sides).
nft_collectornft_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": "0x0a2bbe62c1b6b4a40c511151aeaa8d30e0a2e67992486ae8291767ec8508ace3",
"n_tx": 4286,
"n_successful_tx": 4084,
"n_distinct_epochs": 392,
"n_distinct_sponsors": 3,
"first_seen_cp": 66498128,
"last_seen_cp": 280482255,
"first_seen_ts_ms": 1728331844614,
"last_seen_ts_ms": 1779928787865,
"total_gas_spent_mist": 17329866768,
"n_self_sponsored_tx": 4233,
"n_sponsored_tx": 53,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
20,
19,
4,
2,
21,
1,
18,
22,
5,
3,
23,
0,
6,
17,
16,
9,
7,
10,
8,
15,
14,
13,
11,
12
],
"primary_archetype": "nft_collector",
"labels": [
"nft_collector",
"nft_trader"
],
"label_confidence": [
0.95,
0.727
],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely N. America (Central–Eastern).
area + brightness = call volume; hover for detail