Record a Confirmed Network Fee Without Double Counting

Use one record per included transaction

Create fields for chain, public transaction hash, sender, operation, included block, receipt status and observation time. An approval and a later exchange deserve separate records even when one interface grouped them together. A failed included transaction can still have a network cost, whereas an estimate alone is not a charged transaction. If an original request was replaced, link the records and identify which candidate was actually included.

Retain native-unit cost evidence

Record the receipt’s gas used and effective price where applicable, together with any separate chain-specific fee components. Base distinguishes execution and L1-related costs, so an execution-only multiplication may not reconcile the whole fee. Retain exact values and their units before formatting. If an explorer provides a total, note whether it includes those components rather than silently adding them again and double counting.

Keep economic categories in separate rows

Transferred native value is not itself a network fee. Token input, received output and any disclosed application deduction also need their own entries. For a hypothetical record with a 0.0002 ETH network charge and a separate token output deduction, do not add their raw numbers: their units differ. If you later include a currency conversion, record its source and observation time as an approximation, not a new onchain amount.

Make the record useful without exposing access

Public hashes and addresses can reveal financial activity, so share only the subset needed for the intended purpose. Recovery data, signed transaction payloads and private RPC credentials are not accounting fields. This guide supplies an evidence worksheet, not tax or legal advice. RunixCoin’s public form cannot execute a swap, so its quote and fee disclosure cannot establish a confirmed cost. Mark missing evidence unknown and keep a quoted estimate clearly distinguished from a receipt-backed entry.

References and verification

Reviewed 10 November 2026. Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.

• Ethereum: transaction, receipt and log queries
• Base: fee components
• RunixCoin: current public interface limits