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 dummy `AF_LP` object. Its `init` function is an entry point that calls `amm_interface::create_lp_coin` to create a new LP coin of type `AF_LP`. This suggests the package is primarily for registering a new LP token within an existing AMM system. The `AF_LP` struct itself has no functional fields, indicating it's likely a marker type. There are no other public or entry functions, nor any notable patterns like admin caps or time-gating.
This package defines a dummy `AF_LP` struct. Its single public function, `init`, takes an `AF_LP` object and a `TxContext`. This function immediately calls `amm_interface::create_lp_coin` with the provided `AF_LP` object, a constant `u8` value of 7, and the transaction context. The package's primary purpose appears to be the creation of a new LP coin type, `AF_LP`, within an AMM interface, likely for a liquidity pool. There are no notable patterns like signature gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties present in this module.
This package defines a dummy `AF_LP` object. Its `init` function, which is called once upon package publication, creates a new LP coin using the `amm_interface` module, associating it with the `AF_LP` type and a constant value of 7. There are no other public or entry functions, meaning users cannot interact with this package beyond its initial deployment. The package primarily serves to register a specific LP coin type within an AMM system.
This package defines a dummy `AF_LP` struct, which serves as a type parameter for creating a liquidity pool coin. The `init` function is the only public entry point; it takes an `AF_LP` object and a `TxContext`, then immediately calls `amm_interface::create_lp_coin` to register a new LP coin type. This suggests the package primarily acts as a wrapper to register a specific LP token with an external Automated Market Maker (AMM) interface, likely for a fixed-point LP token. The `AF_LP` object itself is not stored or managed within this module, and no other state is mutated.
The `af_lp` package defines a dummy `AF_LP` struct. Its single `init` function, which is an entry point, calls `amm_interface::create_lp_coin` to create a new LP coin for the `AF_LP` type with a constant value of 3. This suggests the package is a minimal wrapper or placeholder for an LP token within a larger Automated Market Maker (AMM) system, likely used to register a new LP token type. The `init` function mutates the transaction context by creating a new coin. No other notable patterns like signature gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties are present.
True specific-lot profit from 5 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).
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": "0x3828af6d175cdc83db91d8308fc11383d03836063af884116bc2327b29370ce4",
"n_tx": 477,
"n_successful_tx": 477,
"n_distinct_epochs": 64,
"n_distinct_sponsors": 0,
"first_seen_cp": 64446877,
"last_seen_cp": 207237582,
"first_seen_ts_ms": 1727828946106,
"last_seen_ts_ms": 1761970333424,
"total_gas_spent_mist": 2928001632,
"n_self_sponsored_tx": 477,
"n_sponsored_tx": 0,
"gas_price_p50": 750,
"gas_price_p95": 750,
"active_hours_top24": [
19,
23,
17,
6,
4,
5,
1,
18,
3,
20,
7,
0,
15,
22,
21,
2,
8,
16,
12,
9,
14
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"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