Using Foundry: Check Current Gas Price, Estimate Gas, and Send Transactions to the Blockchain

Blockchain development demands precision, especially when it comes to managing transaction costs and ensuring timely execution. One of the most powerful tools in a developer’s arsenal is Foundry, a comprehensive Ethereum development framework that allows for efficient contract testing, deployment, and direct interaction with the blockchain — all from the command line.

With Foundry’s cast command-line tool, developers can check real-time gas prices, estimate transaction costs, and securely send transactions without relying on third-party wallets or web interfaces. This guide walks you through how to use Foundry to monitor gas conditions, estimate fees, and execute transactions with confidence.

Why Use Foundry for On-Chain Interactions?

Interacting with smart contracts or sending ETH doesn’t always require a full development environment or importing private keys into browser wallets. For quick, secure, and scriptable interactions, cast send offers a streamlined alternative.

There are several ways to interact with Ethereum-based contracts:

Direct API calls via Etherscan (limited to read operations).
Programmatic interaction using development tools like Hardhat or Foundry.
Using official dApp interfaces (often less secure due to frontend risks).

For one-off transactions or debugging, Foundry stands out by allowing direct CLI-based execution — no GUI, no extra setup, just clean and auditable commands.

👉 Discover how developers streamline blockchain interactions with powerful tools

Monitor Real-Time Gas Prices Before Sending Transactions

High network congestion can make gas fees spike unexpectedly. Submitting a transaction without checking current conditions may result in slow confirmation or excessive costs.

Check Current Gas Price

Use the cast gas-price command to retrieve the current market rate for gas:

cast gas-price <RPC_URL>

This returns the recommended gas price in wei. To make it more readable, convert it using --to-unit:

cast gas-price --to-unit gwei <RPC_URL>

At the time of writing, this returned approximately 29 Gwei, reflecting average network demand. This value helps you decide whether to proceed immediately or wait for lower fees.

View Base Fee of the Latest Block

On Ethereum post-London Fork (EIP-1559), each block has a base fee, which is burned and adjusts dynamically based on network usage. To view the current base fee:

cast base-fee <RPC_URL>

This provides insight into how congested the network is and helps determine competitive priority fees for faster inclusion.

Estimate Transaction Cost Before Execution

Before spending real funds, estimating gas ensures your transaction won’t fail due to insufficient limits — and gives you full control over expected costs.

Use `cast estimate` to Predict Gas Usage

The syntax is simple:

cast estimate [contract-address] "[function-name(arg-type)]" [arguments] --rpc-url <RPC_URL>

For example:

cast estimate 0xYourContract "transfer(address,uint256)" 0xReceiver 1000000000000000000 --rpc-url https://mainnet.infura.io/v3/YOUR_PROJECT_ID

This returns the estimated gas units required — say, 46,422 units.

Multiply that by the current gas price (e.g., 29 Gwei):

46,422 × 29 Gwei = ~1,346,238 Gwei = 0.001346 ETH

With ETH priced around $3,724, this translates to roughly **$5.01** in transaction cost — an affordable yet significant amount for frequent interactions.

💡 Pro Tip: Always add a buffer (10–20%) to your gas limit to avoid out-of-gas errors during execution.

Send Transactions Securely Using `cast send`

Once you've checked gas prices and estimated costs, it's time to send the transaction.

Key Parameters for `cast send`

cast send [target] "[function()]" [args] \
  --rpc-url <RPC_URL> \
  --private-key <PRIVATE_KEY> \
  --gas-limit 60000 \
  --gas-price 30gwei \
  --value 1ether

Common options include:

--gas-limit: Set maximum gas allowed (default auto-estimated).
--gas-price: Specify price per gas unit (useful for legacy transactions).
--priority-fee: For EIP-1559 transactions, set tip amount.
--value: Send ETH along with the call (in wei, ether, etc.).

Example Use Cases

1. Transfer ETH to an Address

cast send 0xReceiverAddress --value 0.1ether --rpc-url <RPC> --private-key <KEY>

2. Interact With a Smart Contract (No Gas Specified)

cast send 0xContract "mint()" --rpc-url <RPC> --private-key <KEY>

Foundry automatically estimates gas if not provided.

3. Set Custom Gas Limit and Price

cast send 0xContract "setGreeting(string)" "Hello" \
  --gas-limit 100000 \
  --gas-price 35gwei \
  --rpc-url <RPC> \
  --private-key <KEY>

This gives full control over cost and speed.

👉 Learn how top developers optimize their blockchain workflows efficiently

Useful Cast Utilities for Smart Contract Development

Beyond sending transactions, cast includes handy utilities for encoding and decoding data:

Convert Units

cast --to-unit 1ether ether     # → 1
cast --to-unit 1000000000000000000 wei

Encode Function Calls

Generate calldata for external calls:

cast calldata "transfer(address,uint256)" 0x... 100
# Output: 0xa9059cbb000000... (ready to use)

Get Function Selector

Extract the first 4 bytes of the function signature hash:

cast sig "someFunc(address,uint256)"
# Output: 0x8cc5ce99

Decode Function Signatures

Reverse-engineer known selectors:

cast 4byte 0x8cc5ce99
# Returns possible function signatures

Hex and ASCII Conversion

cast --to-base 255 10        # → ff
cast --to-ascii 0x48656c6c6f # → Hello

These tools simplify low-level interactions and debugging without external libraries.

Best Practices for Gas Optimization and Transaction Safety

Always Estimate First: Run cast estimate before any state-changing call.
Check Network Conditions: Use cast gas-price and cast base-fee during peak hours.
Use EIP-1559 When Possible: Prioritize --max-fee-per-gas and --priority-fee over legacy pricing.
Secure Your Private Key: Never hardcode keys in scripts; use environment variables.
Test on Testnets: Validate commands on Sepolia or Holesky before going live.

Frequently Asked Questions (FAQ)

Q: Can I use cast send without specifying gas price?
A: Yes. If omitted, Foundry will auto-estimate gas limits and fetch current network fees to ensure confirmation.

Q: What’s the difference between gas-price and base-fee?
A: gas-price is the total fee paid per unit of gas (including priority tips), while base-fee is the minimum burned portion set by the protocol based on block congestion.

Q: Is it safe to use CLI tools with private keys?
A: Yes — as long as you avoid logging commands and store keys securely (e.g., via .env files). The CLI reduces attack surface compared to browser extensions.

Q: How do I reduce high transaction costs?
A: Monitor gas trends, schedule non-urgent transactions during off-peak hours, and optimize contract logic to reduce gas consumption.

Q: Can I send ERC-20 tokens using cast send?
A: Absolutely. Use the token’s address and encode the transfer(address,uint256) call with proper arguments.

Q: Does Foundry support EIP-1559 transactions?
A: Yes. Use --max-fee-per-gas and --priority-fee-per-gas instead of --gas-price for modern transactions.

👉 Explore advanced blockchain development techniques trusted by professionals

By leveraging Foundry’s cast toolset, developers gain granular control over every aspect of blockchain interaction — from monitoring real-time gas prices to crafting optimized transactions. Whether you're debugging a contract or automating deployments, mastering these CLI commands enhances both efficiency and security.

With accurate estimation, timely execution, and reduced reliance on external platforms, Foundry empowers builders to work faster, safer, and closer to the chain.