What a row is. One balance that changed for rPhMmag9YDcw9d5izQaFRRLfU7EB7WNQky, 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 XRP row it includes the fee. Fee is the fee this account paid, once per transaction (on its XRP 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.