# Export Transaction Logs You can download a log showing all the completed transactions that were made in the organization. Transaction logs can be useful in performing risk analysis, reconciling your company's expenses, and more. ## Download a transaction log for the organization 1. Open the Fordefi web console. 2. In the side menu, click **Transactions.** The Transactions screen opens, displaying the default **All** tab and a list of all transactions. 3. Apply filters, as required. 4. Click **Export** in the upper-right corner. The transactions that correspond to the filters you have set are downloaded in a .csv file. ## Understand the transaction log The transaction log is a .csv file that you can sort and filter. The log is structured so that each line displays a single effect on a vault's balance. Several lines can thus make up a single transaction. For example: alt The following sections describe the details provided in the .csv file. Most columns have the same meaning, across all chains; where the value is chain- or ecosystem-specific, the particulars are provided. ### Transaction ID The unique identifier of the transaction on the Fordefi platform. ### Affected vault ID or affected vault name The vault whose balance this line affects. - *Incoming*: The ID or name of the receiving vault. - *Outgoing*: The ID or name of the source vault. - *Internal*: The transfer produces two lines in the report, one per vault. ### Affected address name or affected address ID - *EVM (and other account-based chains)*: Empty. - *UTXO-based chains (example: Bitcoin)*: Populated, since each row corresponds to a single input or output address. ### Affected vault address The vault's address involved in the transaction. - *EVM (and most account-based chains, including Cosmos)*: The address of the vault. - *Bitcoin*: The address of the specific input or output this row represents. ### Chain The name of the specific blockchain the transaction took place on (examples: "Ethereum", "Bitcoin", "Osmosis"). ### Creation time The time the transaction was created on the platform. For incoming transactions, this is the mined time of the block. ### Created by (name) The name of the user who created the transaction. Empty for incoming transactions. ### Created by (email) The email of the user who signed the transaction. Empty for incoming transactions. ### Approved by (email) The email(s) of the user(s) who approved the transaction under the Transaction Policy in effect at creation time. Empty for incoming transactions. ### Blockchain mine time The time the transaction was mined on the blockchain. ### Transaction source address The signer's blockchain address. - *EVM (and most account-based chains)*: A single signer address. - *Solana, Cosmos*: Multiple signers appear as a comma-separated list. - *Bitcoin*: Empty. ### Transaction source name The signer's name on the Fordefi platform (vault name or address book name), if one exists. - *Solana, Cosmos*: The names of multiple signers appear as a comma-separated list. - *Bitcoin*: Empty. ### Transaction destination address The destination blockchain address of the transaction. - *EVM (and most account-based chains)*: Populated. - *Solana, TON, Aptos, Bitcoin*: Empty. ### Transaction destination name The resolved name of the destination address: vault name, then contact/address-book name. - *EVM (and most account-based chains)*: Populated. - *Solana, TON, Aptos, Bitcoin*: Empty. ### Transaction hash The hash of the transaction on the blockchain. ### Effect type Whether this line is a credit, debit, or fee. - *EVM (and every chain except Bitcoin)*: `Credit`, `Debit`, or `Fees`. - *Bitcoin*: An input is a `Debit`; an output is a `Credit`. Fees are on their own line. ### Effect number The position of this balance effect within its transaction. - *EVM (and most chains)*: The index of the effect relative to the same transaction hash. - *Bitcoin*: Inputs are counted first, then outputs. ### Token name / Token ticker The name and symbol of the token transferred in this effect (example: `Bitcoin` / `BTC` for Bitcoin transactions). ### Token id The token's on-chain NFT id. - *NFT-standard tokens (examples: ERC-721, ERC-1155)*: Populated. - *Fungible tokens and native currencies*: Empty. ### Amount in base units (crypto) The amount transferred, in the token's base units (examples: wei, satoshis). ### Amount in crypto The amount transferred, in the token's principal unit (examples: ETH, USDC, BTC). ### Decimals The number of decimals of the token. ### Token address The token's contract or mint address. - *Native currency (examples: ETH on EVM, SOL on Solana, BTC on Bitcoin)*: Empty. - *Any other token (ERC-20/721/1155, SPL tokens, and the equivalent standards on other chains)*: Populated. ### Token price at mined time The price of the token, in USD, at the time the transaction was mined. ### USD value at mined time The value of the amount transferred, in USD, at the time the transaction was mined. ### Effect source address / Effect source name The address (and its resolved name, if any) that this effect's funds came from. Each row is a `Credit`, `Debit`, or `Fees` effect. - *EVM (and most chains)*: Populated for `Credit` and `Debit` effects; empty for `Fees` effects. - *Bitcoin*: Empty. ### Effect destination address / Effect destination name The address (and its resolved name, if any) that this effect's funds went to, as you'd see it on a block explorer like Etherscan. - *EVM (and most chains)*: Populated for `Credit` and `Debit` effects; empty for `Fees` effects. - *Bitcoin*: Empty.