Skip to main content

Table Metadata

Column Details

Transaction and ledger columnsThis 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.