How to clear a transaction stuck pending at an RPC
A transaction stuck pending because of RPC issues usually means the endpoint accepted but never propagated it, or cannot see it mined. Check the hash, rebroadcast free, then replace if needed.
Crypto Bulletin Newsroom 3 min read
A transaction stays pending because an RPC endpoint may return a hash without propagating the signed transaction, or may fail to report that it was mined. The wallet trusts that endpoint to broadcast and check status, so diagnose the hash first; rebroadcasting the same signed transaction through another RPC is free and safe to try before paying for a replacement.
A returned hash can hide a dropped broadcast
When a wallet submits a signed transaction with eth_sendRawTransaction, the endpoint returns its hash. Ethereum’s JSON-RPC documentation describes that hash as the identifier to track; it does not by itself confirm the transaction reached other nodes’ mempools.
Chainlist is an EVM network directory with chain IDs and RPC endpoints, making its endpoint choices a concrete example of how a wallet can connect to a network through different RPC providers. If an explorer cannot find your transaction hash, the original endpoint may never have propagated it.
Try the same signed raw transaction through a second RPC for the same network. It has the same hash and nonce, so this rebroadcast cannot create a second spend; it gives another endpoint a chance to send the identical transaction onward. This costs no replacement fee, so try it before changing the transaction.
A missing receipt can be a polling problem
eth_getTransactionReceipt returns a receipt by hash, or null when no receipt is found. The wallet may keep asking a faulty or out-of-sync endpoint, while the transaction is already mined and visible elsewhere. Search the hash on a block explorer: a mined result means the wallet’s status display is stale; an unknown result points to a broadcast that did not reach the wider network.
When the explorer shows the transaction as mined, refresh the wallet or switch it to a working RPC for that chain. The receipt lookup and the explorer’s result concern the same hash, so the wallet does not need a replacement transaction.
Replace only when rebroadcast does not clear it
If the explorer still shows the transaction pending and the second RPC rebroadcast did not help, send a replacement with the same nonce. MetaMask’s support instructions describe speeding up or cancelling a pending transaction this way. Geth’s default transaction pool requires a replacement fee at least 10% above the original; other clients may set a different threshold.
A cancellation also uses the same nonce, typically by sending zero native currency to your own address. Only one transaction with that nonce can be mined; later transactions from the same address wait until the lower nonce is mined. If the hash remains unknown and rebroadcast fails, verify the wallet’s selected network and RPC endpoint, then try a healthy endpoint before signing a replacement.