E. Account by account

Account file: r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq

What the XRP Ledger records about r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq, an account in Pheanor's activation tree.

Published

October 2, 2026

Ledger index

107030551

Contents

• How it joins its activation tree
• What it holds, and what it came to
• How it traded
• What its transactions did to the price
• Who it paid, and who paid it
• Destination tags it paid
• Where the CULT it holds came from
• Recorded links to Hodler's activation tree

r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq is an account in Pheanor's activation tree, generation 1. This file is what the ledger records about it. None of it says who holds the account.

How it joins its activation tree

1 creation lead from this account up to a named wallet. Each row is one account paying another into existence. Anyone can pay to create an account for anyone — exchanges do it for customers and services for users — so each row shows a payment, not an owner.

Table 1. Each creation, from this account upward.

every row: download acct-r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq-chain.csv.

What it holds, and what it came to

Table 2. What it holds now, directly and through LP tokens: in each token's main pool, and in any other pool holding it.

every row: download acct-r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq-holdings.csv.

Table 3. Its life in this market, and its result counted in XRP that moved: XRP it paid into the CULT and OBEY market and took out of it, and what it holds now, marked at the pool prices and sold alone into the pools.

every row: download acct-r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq-life.csv.

How it traded

Table 4. Its own buying, selling and pool use of each token, read from its own balance changes. Prices are in XRP per token, from trades against XRP.

every row: download acct-r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq-trading.csv.

What its transactions did to the price

Every transaction of this account that changed a pool's price, by kind. The shares are of that pool's whole rise from opening to its peak, and of its whole move from opening to now; a share below zero pushed the other way.

Table 5. Its transactions that changed each pool's price, by kind, and their share of the price's moves.

every row: download acct-r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq-price-effect.csv.

Who it paid, and who paid it

Table 6. Every account it paid or was paid by, in XRP, the tokens and LP tokens, the largest first. The first 25 are shown; the download has every one.

Showing 25 of 51 rows; every row: download acct-r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq-payments.csv.

Destination tags it paid

A payment to an exchange or service carries a destination tag — a number — so the receiver knows whose balance to credit. The ledger records the number, not the customer, and anybody told a number can pay it; at a marketplace a number may name a sale that many buyers pay. The numbers 0 and 1, which many wallets send by default, and payments to activation tree accounts are left out.

Table 7. Every destination tag it paid, and who else paid the same number to the same receiver.

every row: download acct-r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq-numbers.csv.

Where the CULT it holds came from

Table 8. The CULT it holds now, by where those units had been before, traced first in, first out, as far as the nearest pool.

every row: download acct-r9LXucbnVPniyunxWrbdyBuGbb6rLM9pJq-origins.csv.

Recorded links to Hodler's activation tree

The record shows no CULT or OBEY flow payments, no destination tag paid by 10 accounts or fewer, and no unusual shared behaviour between this account and any account in Hodler's activation tree.