Balance
| Domain | |
|---|---|
| Funded by | |
| Transactions | |
| Last active | |
| Flags | |
| Regular key | |
| Signers |
| Type | From | To | Action | Result | Fee | Hash | Time (UTC) |
|---|
| Issuer | Balance | Token |
|---|
| Token | In circulation | Holders | Trust lines |
|---|
| Counterparty (peer) | Balance | Currency | Peer limit | Owner limit | Peer's settings | Owner's settings | Quality in | Quality out | Ledger entry | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Rippling | Freeze | Auth | Rippling | Freeze | Auth | ||||||||
Hook namespaces hold a hook's data: think of one as a folder for a feature. A hook keeps its state under a 32-byte namespace, usually the SHA-256 of a name its developer chose, so it can always be found again.
Hook states are the pieces of data inside a namespace, each a key-value pair: the key a 32-byte identifier that one ledger command looks up, the value the data itself (its size limit can be raised, see ExtendedHookState). They hold settings, balances, counters - whatever the hook needs.
Projections say how to read that raw data: a named ABI that turns a key's and a value's bytes into typed columns. Anyone signed in can build projections for a hook from its real states and publish them in a manifest, with the hook's name and icon, for everyone who reads this explorer.
| Account | Direction | Counterparty | Amount | Finish after | Cancel after | Status | Ledger entry |
|---|
| Account | Direction | Counterparty | Send max | Expiration | Status | Ledger entry |
|---|
| Account | Direction | Counterparty | Amount | Claimed | Remaining | Settle delay | Closes | Status | Ledger entry |
|---|
| Sells | Buys | Price | Flags | Expiration | Ledger entry |
|---|
| Type | Ledger entry | Flags | Reserve | Last changed | Remarks |
|---|
Who can sign for this account, and how.
Transaction exporter
Every balance this account's transactions changed, one row each, read from the network newest first. Filter them, then download as Excel or CSV.
- Pick the days and fetch
- Filter: by type, result, direction, currency, account - or anything in the search box
- Download what is left, as Excel or CSV
What a row is. One balance that changed for rsFP11jTeEBbxRUG6NmW7jJSeWtwcNgZsg, in one transaction, from its side. A transaction can be several rows - a swap gives one currency for another - one (a failed transaction still costs its fee), or none, when it changed none of this account's balances.
Amount is the change itself, negative when the balance went down; on the XAH row it includes the fee. Fee is the fee this account paid, once per transaction (on its XAH row), and Fee only marks a row that is the fee and nothing else. Direction is IN when the account is the destination, OUT when it sent the transaction, SELF when both, OTHER when neither (an offer of its taken by someone else, say).
Currency is the native code, issuer.CODE for a token - its code readable, or as the ledger stores it with the Raw option - or MPT.id, and CurrencyType says which: native, token or mpt. MPT amounts are in the issuance's base units, unscaled, as the ledger holds them: the same in every file, whatever the issuance's metadata says later.
Fetching goes from the newest transaction to the oldest, straight from the network, in your browser. A long history takes a while: the network limits how fast one visitor may read, and the tool waits whenever it is asked to, and reconnects if the connection drops. Stop keeps what has been read so far.
Filters - the chips, the beside a value, and the search box - narrow the downloads as well as the table. Links in the table open in a new tab, so the export stays here.
Files. The CSV keeps every digit. In Excel, amounts are numbers, which Excel holds to 15 significant digits; ids and codes stay text. Everything is in your browser's memory: for a very long history, export a range of days at a time.
Provided as is, for your own use and at your own responsibility.