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 facilitates token swaps, primarily managing `SwapSession` objects and interacting with `LiquidStakingInfo` objects. The `swap` entry function acts as a router, calling either `swap_a_to_b` or `swap_b_to_a` based on a boolean argument. `swap_a_to_b` takes SUI from a `SwapSession`, mints a generic `Ty0` liquid staking token using a `LiquidStakingInfo` object, and merges the resulting `Ty0` balance back into the `SwapSession`. Conversely, `swap_b_to_a` takes a generic `Ty0` token from a `SwapSession`, redeems it for SUI using `LiquidStakingInfo`, and merges the SUI balance back into the `SwapSession`. Both swap functions emit a `SwapEvent` via an `aggregator` module, detailing the swap amounts and the `LiquidStakingInfo` object involved. The `SuiSystemState` object is passed to liquid staking functions, suggesting interaction with the Sui
This package, `aftermath_lsd_router`, primarily manages `SwapSession` objects, which are used to facilitate token swaps. The public `swap` function acts as a router, conditionally calling either `swap_a_to_b` or `swap_b_to_a` based on a boolean argument. `swap_a_to_b` takes SUI from a `SwapSession`, stakes it via a `StakedSuiVault` and `SuiSystemState`, and returns AFSUI to the `SwapSession`, potentially involving a `ReferralVault` and `Safe<TreasuryCap<AFSUI>>`. Conversely, `swap_b_to_a` takes AFSUI from a `SwapSession`, unstakes it via a `StakedSuiVault` and `Treasury`, and returns SUI to the `SwapSession`, also potentially involving a `ReferralVault` and `Safe<TreasuryCap<AFSUI>>`. Both swap functions emit a `swap_event` to record the transaction details.
This package, `turbos_fun_router`, facilitates token swaps using a `SwapSession` object to manage balances and a `Configuration` object for swap parameters. The primary public function, `swap`, acts as a router, calling either `swap_a_to_b` or `swap_b_to_a` based on a boolean argument. These functions perform token exchanges, either SUI for a generic token `Ty0` or vice-versa, by interacting with the `turbospump` module. They take an input amount, execute the swap, and then either return any remaining input balance to the sender or merge it back into the `SwapSession`. A notable pattern is the emission of a `swap_event` after each successful swap, detailing the swap session, configuration ID, and amounts.
This package facilitates token swaps through CPMM (Constant Product Market Maker) pools. It primarily manages `Coin` objects and interacts with `SwapSession`, `Pool`, `PoolRegistry`, `ProtocolFeeVault`, `Treasury`, `InsuranceFund`, and `ReferralVault` objects from other modules. The public `swap` function acts as a router, calling either `swap_a_to_b` or `swap_b_to_a` based on a boolean argument, effectively allowing users to swap between two token types within a given pool. Both `swap_a_to_b` and `swap_b_to_a` take an input `Coin` from the `SwapSession`, perform a swap using `swap::swap_exact_in`, and then merge the resulting output `Coin` back into the `SwapSession`. These swap operations mutate the `Pool`, `Treasury`, and `InsuranceFund` objects, and emit a swap event via the `aggregator` module. The package integrates with various vault-like structures for fees and referrals.
This package, ferra_dlmm_router, facilitates token swaps on a decentralized exchange. Its primary object type is the LBPair, representing a liquidity pool for two token types (Ty0, Ty1). The public 'swap' function allows users to exchange tokens by calling either 'swap_a_to_b' or 'swap_b_to_a' based on the desired swap direction. These internal functions mutate the provided LBPair object by updating its token balances and also interact with a SwapSession object to manage the swap process and emit swap events. The package uses a GlobalConfig object for configuration and integrates with the aggregator module for managing token balances within the swap session.
Wallets that share a funder, were co-funded by the same personal-scale source, or land in the same behavioral cluster. A heuristic, not proof of common control.
area + brightness = call volume; hover for detail
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": "0xe5850acfac86e0c855b1382f25eda46eb0d75c65b8939e95e3bc76a346853472",
"n_tx": 262,
"n_successful_tx": 196,
"n_distinct_epochs": 29,
"n_distinct_sponsors": 0,
"first_seen_cp": 213795076,
"last_seen_cp": 248181112,
"first_seen_ts_ms": 1763539647308,
"last_seen_ts_ms": 1771905021660,
"total_gas_spent_mist": 3763276832,
"n_self_sponsored_tx": 262,
"n_sponsored_tx": 0,
"gas_price_p50": 505,
"gas_price_p95": 515,
"active_hours_top24": [
9,
7,
8,
4,
6,
3,
10,
5,
11,
2
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Tinted amber on the bubble map when they appear in the expanded graph.
Top active hours by UTC. Circadian peak → likely E. Asia / Oceania.