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 defines a single dummy struct, `RMOS`, which serves as a type parameter for a bonding curve. The `init` function creates a new bonding curve using the `bonding_curve::create_bonding_curve` function, initializing it with various metadata including a name, description, URL, and social media links. It also includes a large constant byte string, likely representing some form of identifier or key. Finally, the `BondingCurveStartCap<RMOS>` object, which grants initial control over the bonding curve, is transferred to the transaction sender. This package primarily manages a bonding curve, with the `init` function setting up its initial state and transferring administrative control.
This package defines a single dummy object type, `RMOS`, which has no functional purpose beyond being a type parameter. The `init` function is the only public/entry point and it creates a `BondingCurveStartCap<RMOS>` object by calling `bonding_curve::create_bonding_curve`. This capability object is then transferred to the transaction sender. The `create_bonding_curve` function is called with various string literals for name, description, symbol, and social media links, along with a large byte string which likely represents the bonding curve parameters. This module primarily acts as an initializer for a bonding curve associated with the `RMOS` type.
This package defines a single module `rmos` which manages a dummy `RMOS` object. The `init` function, which is likely called once during package deployment, creates a `BondingCurveStartCap<RMOS>` object using the `bonding_curve` module. This bonding curve is initialized with metadata including a name, description, image URL, and social media links (website, Twitter, Discord, Telegram). The `BondingCurveStartCap` is then transferred to the sender of the transaction. The `RMOS` struct itself contains only a boolean `dummy_field`, suggesting its primary purpose is as a type parameter for the bonding curve.
{
"wallet": "0x749ea3cfc7589eaae178468687526eb31377a272239d2e0bc5cd42a94c1a42bc",
"n_tx": 1805,
"n_successful_tx": 1798,
"n_distinct_epochs": 114,
"n_distinct_sponsors": 2,
"first_seen_cp": 1576534,
"last_seen_cp": 280168726,
"first_seen_ts_ms": 1683125379535,
"last_seen_ts_ms": 1779857802210,
"total_gas_spent_mist": 3971301216,
"n_self_sponsored_tx": 1799,
"n_sponsored_tx": 6,
"gas_price_p50": 820,
"gas_price_p95": 820,
"active_hours_top24": [
5,
3,
4,
1,
0,
2,
9,
14,
13,
6,
15,
7,
12,
8,
16,
11,
10,
23,
17
],
"primary_archetype": null,
"labels": [],
"label_confidence": [],
"bot_score": 0,
"bot_signals": [],
"cex_label": null
}Top active hours by UTC. Circadian peak → likely W. N. America (Pacific/Mountain).
area + brightness = call volume; hover for detail