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` struct. Its `init` function, which is likely an entry point, creates a new LP coin of type `AF_LP` by calling `amm_interface::create_lp_coin`. This suggests the package is intended to integrate with an Automated Market Maker (AMM) system, specifically to define a new Liquidity Pool (LP) token. The `AF_LP` struct itself has no functional fields, indicating it's primarily a type marker for the LP coin. The package doesn't manage any other objects directly, nor does it exhibit complex patterns like signature gating, time-gating, or admin caps.
This package defines a dummy `AF_LP` object. Its single public function, `init`, takes an `AF_LP` object and a `TxContext` as input. The `init` function immediately calls `amm_interface::create_lp_coin` with the provided `AF_LP` object, a constant value of 7, and the `TxContext`. This suggests the package's primary purpose is to initialize or register an `AF_LP` type within an Automated Market Maker (AMM) system, likely creating a liquidity pool coin for it. There are no notable patterns like signature gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties present in this bytecode.
The `af_lp` package defines a dummy `AF_LP` struct. Its single public function, `init`, takes an `AF_LP` object and a `TxContext` and calls `amm_interface::create_lp_coin` with the `AF_LP` object, a constant value of 7, and the transaction context. This suggests `af_lp` acts as a placeholder or wrapper for creating a liquidity pool coin within an AMM (Automated Market Maker) system, likely using the `AF_LP` type as the underlying asset for the LP coin. The package itself doesn't manage any objects directly beyond passing its dummy struct to another module.
This package defines a dummy `AF_LP` object. Its `init` function, which is called once during package deployment, creates a new LP coin using the `amm_interface::create_lp_coin` function, passing the dummy `AF_LP` object as the coin type. This suggests `af_lp` is primarily a placeholder module for defining a specific LP token type within a larger AMM system. The module itself doesn't manage any other objects or have public/entry functions beyond initialization.
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 immediately calls `amm_interface::create_lp_coin` with the provided `AF_LP` object, a constant value of 8, and the `TxContext`. This suggests the package's primary purpose is to initialize a new LP coin of type `AF_LP` within an AMM (Automated Market Maker) system, likely representing a liquidity provider token. There are no notable patterns like signature/allowlist gating, time-gating, dynamic fields, admin caps, vault/escrow, or royalties present in this module.
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": "0x0a93213c4cbfac6f7b8573e15d66aa7a9cca2d0de63eeb633be0e9a05fb1e3b7",
"n_tx": 420,
"n_successful_tx": 412,
"n_distinct_epochs": 45,
"n_distinct_sponsors": 0,
"first_seen_cp": 170105206,
"last_seen_cp": 282416392,
"first_seen_ts_ms": 1753109937405,
"last_seen_ts_ms": 1780438192051,
"total_gas_spent_mist": 23647020324,
"n_self_sponsored_tx": 420,
"n_sponsored_tx": 0,
"gas_price_p50": 500,
"gas_price_p95": 710,
"active_hours_top24": [
6,
22,
17,
1,
21,
15,
16,
14,
5,
19,
7,
20,
18,
13,
0,
12,
23,
2,
8,
4,
11,
3,
9,
10
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely Atlantic / E. South America.
area + brightness = call volume; hover for detail