View and clear the transaction pool with basectl txpool

View pending and queued transactions and clear the transaction pool on a Base execution-layer node with basectl txpool.

basectl txpool lets you look at and clear the transaction pool on a single execution-layer (EL) node. By default it uses the RPC URL in your config; pass --el-rpc <URL> to target a specific node. The global --conductor-rpc flag has no effect here.

Commands

• basectl txpool pending [SENDER] lists pending transactions (optionally for one sender).
• basectl txpool queued [SENDER] lists queued transactions (optionally for one sender).
• basectl txpool all [SENDER] lists both pending and queued transactions.
• basectl txpool clear clears the entire pool.
• basectl txpool clear --sender <ADDRESS> drops every transaction from one sender.

The default output shows how many transactions are in each part of the pool, a per-sender summary, and one row per transaction with its sender, nonce, hash, destination, value, gas, fee, and input size.

clear cannot drop a single transaction by hash in this version.

Flags

Read-only commands accept:

Flag	Description
--el-rpc <URL>	Use a specific execution-layer RPC URL instead of the one in your config.
--json	Print JSON with the network, RPC URL, scope, optional sender, counts, per-sender summaries, and decoded transaction rows.
--raw	Add to --json to print the raw pool contents from the node. Using --raw without --json is an error.

Clearing the pool accepts:

Flag	Description
--sender <ADDRESS>	Drop only this sender’s transactions instead of the whole pool.
--el-rpc <URL>	Use a specific execution-layer RPC URL. Clearing usually requires a node with admin methods enabled.
--yes	Skip the confirmation prompt. By default, clear prints exactly what it will remove and waits for y or yes; anything else cancels.
--json	Print the result as JSON. Requires --yes so an automated run never waits for input.

txpool clear removes transactions from the node’s pool and usually requires a node with admin methods enabled. Double-check the target node and scope before adding --yes.

Examples

View the pool

# List all pending transactions
basectl -c sepolia txpool pending

# List queued transactions for one sender
basectl -c sepolia txpool queued 0xYourSenderAddress

# List pending and queued transactions as JSON
basectl -c sepolia txpool all --json | jq '{pending: .pendingCount, queued: .queuedCount}'

Clear the pool

# Clear the whole pool (asks for confirmation first)
basectl -c sepolia txpool clear --el-rpc https://your-el.example/

# Drop only one sender's transactions, no prompt, print JSON
basectl -c sepolia txpool clear --sender 0xYourSenderAddress --el-rpc https://your-el.example/ --yes --json | jq .

Related

• basectl overview
• Manage peers (p2p)
• Node troubleshooting