Sent transaction: Why Etherscan can’t find it yet
Why does a sent transaction not show up on Etherscan? A hash can exist before any node accepts it; private routing can keep it off the public tracker.
The Chain Times Desk3 min read

Etherscan may not show a sent Ethereum transaction because its nodes have not seen it, or because no node accepted it; private routing can also keep it out of the public mempool. A transaction hash is made from the signed transaction before broadcast, so seeing a hash in your wallet does not prove that any node received it.
Ethereum.org describes the usual path: a wallet signs a transaction, broadcasts it to the network, and a validator includes it in a block. Etherscan can show a pending transaction once its nodes have heard about it. Until then, a search for the hash may return “not found,” even though your wallet produced the hash.
Private routing keeps a pending transaction off Etherscan
A private route sends a transaction to block builders without first sharing it through the public mempool, the pool of transactions that Ethereum nodes share with one another. Flashbots Protect is one example: its private transaction routing sends transactions to builders, so they may stay invisible on Etherscan until a block includes them. The flashbots RPC is a concrete example of that private route.
Flashbots’ documentation says Protect transactions skip the public mempool. Take a swap sent through Protect: it can show “not found” on Etherscan for several blocks, then appear directly as confirmed when included. For a transaction sent this way, look at the RPC provider’s own status page to see whether it is still pending or was included.
- Publicly broadcast: a node has seen it, but it may still be pending.
- Privately routed: it may be waiting with a builder, unseen by Etherscan.
- Not accepted: no node kept it in its transaction pool.
These cases explain why the hash alone cannot tell you where the transaction is. First identify how your wallet sent it, then use the matching tracker or status page.
Rejected transactions need a fee or nonce correction
A transaction that nodes reject or drop will not appear as pending on Etherscan. Ethereum.org explains that transactions carry a nonce, a sequential count of an account’s transactions, and a fee. If the max fee is below the current base fee, a node will not accept the transaction into its pool. A nonce gap can also hold it back: a later transaction cannot be processed while an earlier nonce is missing.
Say your wallet shows a hash, but neither Etherscan nor your RPC provider finds it. The hash may have been calculated before broadcast, while the transaction failed to reach or pass a node. If the fee is too low, correct it; if a nonce is missing or stuck, resolve that first. Then resend and look up the new hash. Searching the old hash cannot make a transaction that no node accepted appear.
Start by checking the route your wallet used. For a private transaction, check the provider’s status; for a public one, search the hash again after it has had time to propagate. This tells you whether to wait for inclusion or fix the transaction before resending.