Fee conditions, nonce gaps and propagation can all delay inclusion.
LET’S PICTURE IT
A form might wait because its postage is insufficient, an earlier numbered form is missing, or the relevant office has not received it.
SEE IT FOR YOURSELF
Illustration · no network calls
Prepare
→
Sign
→
Share
→
Include
→
Finalize
Maya prepares an instruction: send 0.01 pretend ETH to Leo.
A local simulation. Nothing is signed or sent to a network.
Fee caps can become insufficient
For a standard EIP-1559 transaction, a maximum fee cap below the current block base fee cannot cover that base fee. A previously acceptable candidate can therefore wait when conditions change.
The account sequence can block progress
A later nonce cannot ordinarily execute before the account reaches that sequence position. Increasing a later transaction’s fees does not automatically repair an unresolved earlier nonce.
Visibility and inclusion are separate
A provider may have accepted a submission while other nodes do not yet know it. A transaction might be dropped from a local pool or superseded. Lack of a receipt needs investigation rather than an immediate assumption of successful cancellation.
Inspect before repeating
Repeatedly creating new payments can produce several valid transactions with different nonces. Understand the current account sequence and wallet’s replacement behavior before taking action. This site explains the mechanics but does not query or manage pending transactions.