Enriched History Operations
Table Metadata​
| Property | Configuration |
|---|---|
| Natural Key(s) | op_id |
| Partition Field(s) | closed_at (DAY partition) |
| Clustered Field(s) | ledger_sequence, transaction_id, op_account_id, type |
| Documentation | dbt_docs |
Column Details​
| Name | Description | Data Type | Domain Values | Required? | Source Table | Notes |
|---|---|---|---|---|---|---|
| account | The new resulting account address that is created and funded (create operation) The account address that is being removed and merged into another account (merge operation) | string | history_operations | Part of the original details object in the history_operations table | ||
| amount | Float representation of the amount of an asset sent/offered/etc | float | history_operations | |||
| asset_code | The 4 or 12 character code representation of the asset on the network | string | history_operations | |||
| asset_issuer | The account address of the original asset issuer that created the asset | string | history_operations | |||
| asset_type | The identifier for type of asset code, can be a alphanumeric with 4 characters, 12 characters or the native asset to the network, XLM. | string |
| history_operations | ||
| authorize | Indicates whether the trustline is authorized. 0 is the account is not authorized to transact with the asset in any way. 1 if the account is authorized to transact with the asset. 2 if the account is authorized to maintain orders, but not to perform other transactions. | boolean | history_operations | |||
| balance_id | The unique identifier of the claimable balance. The id is comprised of 8 character type code + SHA-256 hash of the history operation id that created the balance. The balance id can be joined back to the claimable_balances table to gather more details about the balance | string | history_operations | |||
| buying_asset_code | The 4 or 12 character code representation of the asset that is either bought or offered to buy in a trade | string | history_operations | |||
| buying_asset_issuer | The account address of the original asset issuer that created the asset bought or offered to buy | string | history_operations | |||
| buying_asset_type | The identifier for type of asset code, can be a alphanumeric with 4 characters, 12 characters or the native asset to the network, XLM. | string |
| history_operations | ||
| from | The account address from which the payment originates (the sender account) | string | history_operations | |||
| funder | When a new account is created, an account address "funds" the new account | string | history_operations | |||
| high_threshold | The sum of the weight of all signatures that sign a transaction for the high threshold operation. The weight must exceed the set threshold for the operation to succeed. | integer | history_operations | Each operation falls under a specific threshold category: low, medium or high. Thresholds define the level of privilege an operation needs in order to succeed (this is a security measure) Low Security: Allow Trust, Set Trust Line Flags, Bump Sequence and Claim Claimable Balance Medium Security: Everything Else High Security: Account Merge, Set Options | ||
| home_domain | The home domain used for the stellar.toml file discovery | string | history_operations | |||
| inflation_dest | The account address specifying where to send inflation funds. The concept of inflation on the network has been discontinued | string | history_operations | Inflation was retired from the network in 2019. | ||
| into | The account address receiving the deleted account's lumens. This is the account in which the intended deleted account will be merged | string | history_operations | |||
| limit | The upper bound amount of an asset that an account can hold | float | history_operations | |||
| low_threshold | The sum of the weight of all signatures that sign a transaction for the low threshold operation. The weight must exceed the set threshold for the operation to succeed. | integer | history_operations | Each operation falls under a specific threshold category: low, medium or high. Thresholds define the level of privilege an operation needs in order to succeed (this is a security measure) Low Security: Allow Trust, Set Trust Line Flags, Bump Sequence and Claim Claimable Balance Medium Security: Everything Else High Security: Account Merge, Set Options | ||
| master_key_weight | An accounts private key is called the master key. For signing transactions, the account holder can specify a weight for the master key, which contributes to thresholds validation when processing a transaction | integer | Integers from 1 to 255 | history_operations | ||
| med_threshold | The sum of the weight of all signatures that sign a transaction for the medium threshold operation. The weight must exceed the set threshold for the operation to succeed. | integer | history_operations | Each operation falls under a specific threshold category: low, medium or high. Thresholds define the level of privilege an operation needs in order to succeed (this is a security measure) Low Security: Allow Trust, Set Trust Line Flags, Bump Sequence and Claim Claimable Balance Medium Security: Everything Else High Security: Account Merge, Set Options | ||
| name | The manage data operation allows an account to write and store data directly on the ledger in a key value pair format. The name is the key for a data entry. | string | history_operations | |||
| offer_id | The unique id for the offer. This id can be joined with the offers table | integer | history_operations | |||
| path | Path payments maximize the best exchange rate path when sending money from one asset to another asset. The intermediary assets that this path hops through will be reported in the record. This feature is especially useful when the market between the original asset pair is illiquid | array[record] | history_operations | Up to 6 paths are permitted for a single payment. Example: sending EUR -> MXN could look like EUR -> BTC -> CNY -> XLM -> MXN to maximize the best exchange rate Payments are atomic, so if an exchange in the middle of a path payment fails, the entire payment will fail which means the user will keep their original funds. They will not be stuck with an intermediary asset in the event of payment failure. | ||
| price | The ratio of selling asset to buying asset. This is a number representing how many units of a selling asset it takes to get 1 unit of a buying asset | float | history_operations | |||
| d | Precise representation of the buy and sell price of a trade. The d is the denominator. When taken with n/d you will get the price | integer | history_operations | |||
| n | Precise representation of the buy and sell prices of a trade. The n is the numerator. When taken with n/d you will get the price. | integer | history_operations | |||
| selling_asset_code | The 4 or 12 character code representation of the asset that is either sold or offered to sell in a trade | string | history_operations | |||
| selling_asset_issuer | The account address of the original asset issuer that created the asset sold or offered to sell | string | history_operations | |||
| selling_asset_type | The identifier for type of asset code, can be a alphanumeric with 4 characters, 12 characters or the native asset to the network, XLM. | string |
| history_operations | ||
| set_flags | Array of numeric values of the flags set for a given trustline in the operation | array[integer] |
| history_operations | ||
| set_flags_s | Array of string values of the flags set for a given trustline in the operation | array[string] |
| history_operations | ||
| signer_key | The address of the signer which is no longer sponsored | string | history_operations | |||
| signer_weight | The weight of the new signer. For transactions, multiple accounts can sign a transaction from a source account. This weight contributes towards calculating whether the transaction exceeds the specified threshold weight to complete the transaction | integer | history_operations | |||
| source_amount | The originating amount sent designated in the source asset | float | history_operations | |||
| source_asset_code | The 4 or 12 character code representation of the asset that is originally sent | string | history_operations | |||
| source_asset_issuer | The account address of the original asset issuer that created the asset sent | string | history_operations | |||
| source_asset_type | The identifier for type of asset code, can be a alphanumeric with 4 characters, 12 characters or the native asset to the network, XLM. | string |
| history_operations | ||
| source_max | The maxium amount to be sent, designated in the source asset | float | history_operations | |||
| starting_balance | The amount of XLM to send to the newly created account. The account starting balance will need to exceed the minimum balance necessary to hold an account on the Stellar Network | float | history_operations | |||
| to | The address of the account receiving the payment funds | string | history_operations | |||
| trustee | The issuing account address (only present for credit asset types) | string | history_operations | |||
| trustor | The trusting account address, or the account being authorized or unauthorized | string | history_operations | |||
| trustline_asset | The asset of the trustline which is no longer sponsored | string | history_operations | |||
| value | The manage data operation allows an account to write and store data directly on the ledger in a key value pair format. The value is the value of a key for a data entry. | string | history_operations | |||
| clear_flags | Array of numeric values of the flags cleared for a given trustline in the operation. If the flag was originally set, this will delete the flag | array[integer] |
| history_operations | ||
| clear_flags_s | Array of string values of the flags cleared for a given trustline in the operation. If the flag was originally set, this will delete the flag | array[string] |
| history_operations | ||
| destination_min | The minimum amount to be received, designated in the expected destination asset | string | history_operations | |||
| bump_to | The new desired value of the source account's sequence number | string | history_operations | |||
| sponsor | The account address of another account that maintains the minimum balance in XLM for the source account to complete operations | string | history_operations | |||
| sponsored_id | The account address of the account which will be sponsored | string | history_operations | |||
| begin_sponsor | The account address of the account which initiated the sponsorship | string | history_operations | |||
| authorize_to_maintain_liabilities | Indicates whether the trustline is authorized. 0 is the account is not authorized to transact with the asset in any way. 1 if the account is authorized to transact with the asset. 2 if the account is authorized to maintain orders, but not to perform other transactions. | boolean | history_operations | |||
| clawback_enabled | Indicates whether the asset can be clawed back by the asset issuer | boolean | history_operations | |||
| liquidity_pool_id | Unique identifier for a liquidity pool | string | history_operations | |||
| reserve_a_asset_type | The identifier for type of asset code, can be a alphanumeric with 4 characters, 12 characters or the native asset to the network, XLM. | string |
| history_operations | ||
| reserve_a_asset_code | The 4 or 12 character code representation of the asset of one of the two asset pairs in a liquidity pool | string | history_operations | |||
| reserve_a_asset_issuer | The account address of the original asset issuer that created one of the two asset pairs in the liquidity pool | string | history_operations | |||
| reserve_a_max_amount | The maximum amount of reserve a that can be deposited into the pool. | float | history_operations | |||
| reserve_a_deposit_amount | The amount of reserve a that ended up actually deposited into the pool | float | history_operations | |||
| reserve_b_asset_type | The identifier for type of asset code, can be a alphanumeric with 4 characters, 12 characters or the native asset to the network, XLM. | string |
| history_operations | ||
| reserve_b_asset_code | The 4 or 12 character code representation of the asset of one of the two asset pairs in a liquidity pool | string | history_operations | |||
| reserve_b_asset_issuer | The account address of the original asset issuer that created one of the two asset pairs in the liquidity pool | string | history_operations | |||
| reserve_b_max_amount | The maximum amount of reserve b that can be deposited into the pool. | float | history_operations | |||
| reserve_b_deposit_amount | The amount of reserve b that ended up actually deposited into the pool. | float | history_operations | |||
| min_price | The floating point value indicating the minimum exchange rate for this deposit operation. Reported as Reserve A / Reserve B | float | history_operations | |||
| min_price_r | A fractional representation of the prices of the two assets in a pool. The n is the numerator (value of asset a) and the d is the denominator (value of asset b) | array[record] | history_operations | |||
| max_price | The floating point value indicating the maximum exchange rate for this deposit operation. Reported as Reserve A / Reserve B | float | history_operations | |||
| max_price_r | A fractional representation of the prices of the two assets in a pool. The n is the numerator (value of asset a) and the d is the denominator (value of asset b) | array[record] | history_operations | |||
| shares_received | A floating point number representing the number of pool shares received for this deposit. A pool share is a compilation of both asset a and asset b reserves. It is not possible to own only asset a or asset b in a pool | float | history_operations | |||
| reserve_a_min_amount | The minimum amount of reserve a that can be withdrawn from the pool. | float | history_operations | |||
| reserve_b_min_amount | The minimum amount of reserve b that can be withdrawn from the pool. | float | history_operations | |||
| shares | The number of shares withdrawn from the pool. It is not possible to withdraw only asset a or asset b, equal value must be withdrawn from the pool | float | history_operations | |||
| reserve_a_withdraw_amount | The amount of reserve a that ended up actually withdrawn from the pool. | float | history_operations | |||
| reserve_b_withdraw_amount | The amount of reserve b that ended up actually withdrawn from the pool. | float | history_operations | |||
| op_id | Unique identifier for an operation | integer | history_operations | |||
| op_source_account | The account address that originates the operation | string | history_operations | |||
| op_source_account_muxed | If an account is multiplexed (muxed), the virtual account address that originates the operation | string | history_operations | |||
| transaction_id | The transaction identifier in which the operation executed. There can be up to 100 operations in a given transaction | integer | history_operations | |||
| type | The number indicating which type of operation this operation executes | integer | history_operations | |||
| type_string | The string indicating which type of operation this operation executes | string | history_operations | |||
| op_account_id | The address of the account which is no longer sponsored | string | history_operations | Flattened from details.account_id. Cluster Field. | ||
| op_account_muxed | The virtual address of the account if the account is multiplexed | string | history_operations | Flattened from details.account_muxed. | ||
| op_account_muxed_id | Integer representation of the virtual address of the account if the account is multiplexed | string | history_operations | Flattened from details.account_muxed_id. | ||
| asset | The asset available to be claimed in the form of "asset_code:issuing_address". If the claimable balance is in XLM, the value is native | string | history_operations | |||
| claimant | The account address of the account which claimed the claimable balance | string | history_operations | |||
| claimant_muxed | If the account is multiplexed, the virtual address of the account which claimed the claimable balance | string | history_operations | |||
| claimant_muxed_id | If the account is multiplexed, an integer representation of the muxed account which claimed the balance | string | history_operations | |||
| claimants | An unstructured field that lists account addresses eligible to claim a balance and the conditions which must be met to claim | array[record] | history_operations | |||
| data_account_id | The account address of the account whose data entry is no longer sponsored | string | history_operations | |||
| data_name | The name of the data entry which is no longer sponsored | string | history_operations | |||
| signer_account_id | The address of the account of the signer no longer sponsored | string | history_operations | |||
| trustline_account_id | The address of the account whose trustline is no longer sponsored | string | history_operations | |||
| from_muxed | If the account is multiplexed, the virtual address of the sender account | string | history_operations | |||
| from_muxed_id | If the account is multiplexed, the integer representation of the virtual address of the sender account | string | history_operations | |||
| to_muxed | If the account is multiplexed, the virtual address of the account receiving the payment | string | history_operations | |||
| to_muxed_id | If the account is multiplexed, the integer representation of the virtual address of the recipient account | string | history_operations | |||
| funder_muxed | If the account is multiplexed, the virtual address of the account funding the new account | string | history_operations | |||
| funder_muxed_id | If the account is multiplexed, the integer representation of the virtual address of the funding account | string | history_operations | |||
| into_muxed | If the account is multiplexed, the virtual address of the account receiving the deleted account's lumens | string | history_operations | |||
| into_muxed_id | If the account is multiplexed, the integer representation of the account receiving the deleted account's lumens | string | history_operations | |||
| trustee_muxed | If the issuing account address is multiplexed, the virtual address | string | history_operations | |||
| trustee_muxed_id | If the issuing account address is multiplexed, the integer representation of the virtual address | string | history_operations | |||
| trustor_muxed | If the trusting account is multiplexed, the virtual address of the account | string | history_operations | |||
| trustor_muxed_id | If the trusting account is multiplexed, the integer representation of the virtual address | string | history_operations | |||
| begin_sponsor_muxed | If the initiating sponsorship account is multiplexed, the virtual address | string | history_operations | |||
| begin_sponsor_muxed_id | If the initiating sponsorship account is multiplexed, the integer representation of the virtual address | string | history_operations | |||
| soroban_operation_type | The type of Soroban operation that is invoked within a host function | string |
| history_operations | Flattened from details.type. | |
| function | The function type invoked by the host operation | string | history_operations | |||
| address | The wallet address used to create and deploy a Soroban contract instance | string | history_operations | |||
| contract_id | The unique identifier of the deployed contract instance. Each custom Soroban contract and deployed SAC token will have a unique contract id | string | history_operations | |||
| contract_code_hash | The hex-encoded SHA-256 hash that represents the contract code's XDR-encoded form | string | history_operations | |||
| extend_to | The number of ledgers in which the Soroban ledger entry is extended | integer | history_operations | |||
| asset_balance_changes | The balance changes applied to an account or contract from an invoke host function | array[record] | history_operations | |||
| parameters | The parameters passed to the function call for a Soroban contract. These are base64 encoded XDR | array[record] | history_operations | |||
| parameters_decoded | The decoded human-readable parameters passed to a function call for a Soroban contract | array[record] | history_operations | |||
| operation_result_code | The result code returned when an operation is applied. This code is helpful for understanding failed operations | string | history_operations | |||
| operation_trace_code | The trace code returned when an operation is applied to the Stellar Network. This code is helpful for understanding failure types | string | history_operations |
This table also carries transaction-level columns from History Transactions (closed_at, ledger_sequence, transaction_hash, txn_account, txn_created_at, txn_operation_count, account_sequence, account_muxed, max_fee, new_max_fee, memo, memo_type, time_bounds, ledger_bounds, successful, transaction_result_code, fee_account, fee_account_muxed, fee_charged, extra_signers, tx_signers, min_account_sequence, min_account_sequence_age, min_account_sequence_ledger_gap, resource_fee, resource_fee_refund, refundable_fee, non_refundable_resource_fee_charged, refundable_resource_fee_charged, rent_fee_charged, inclusion_fee_bid, inclusion_fee_charged, soroban_resources_instructions, soroban_resources_read_bytes and soroban_resources_write_bytes) and ledger-level columns from History Ledgers (ledger_hash, previous_ledger_hash, ledger_id, ledger_operation_count, transaction_count, successful_transaction_count, failed_transaction_count, total_coins, fee_pool, base_fee, base_reserve, max_tx_set_size, protocol_version, node_id, signature, soroban_fee_write_1kb and total_byte_size_of_bucket_list), plus the batch metadata columns batch_id, batch_run_date and airflow_start_ts and the raw details_json record.
Those columns carry the same meaning here as they do in their source tables and are not repeated above.
Not every column of the source tables is carried over. In particular the Protocol 23 additions soroban_resources_disk_read_bytes and soroban_resources_archived_entries (History Transactions) and total_byte_size_of_live_soroban_state (History Ledgers) are not selected by this model; query the bronze tables directly for those.