Czytanie on-chain
The mempool: the network's waiting room
Before a transaction reaches a block it sits in the mempool, the set of unconfirmed transactions each node keeps. That waiting room is public and readable.
What a mempool view shows
Visualisations show forming blocks grouped by fee level, so you can see the rate needed for next-block inclusion.
That is more useful than a single recommended fee.
Why transactions get stuck
A fee below the current minimum is ignored while higher bids queue; once congestion clears it may still confirm.
Some nodes drop transactions after a while, in which case the coins simply never left your address.
- Fee too low: wait or replace
- Nonce gap on Ethereum blocks later transactions
- Dropped from mempool: resend
Speeding up: RBF and CPFP
Bitcoin allows replace-by-fee, or child-pays-for-parent where the receiver attaches a high-fee child transaction.
On Ethereum you replace by reusing the same nonce with a higher price.
Timing in practice
For non-urgent transfers, waiting for a quiet moment can cut fees several times over.
For time-critical actions, overpaying is insurance, not waste.
Najczęstsze pytania
What is the mempool?
The set of valid but unconfirmed transactions nodes hold until a miner or validator includes them.
How long does a transaction stay there?
Seconds to days depending on fee and congestion; many nodes drop them after about two weeks.
Can I speed up a stuck transaction?
Often yes, via replace-by-fee or by reusing the same nonce with a higher fee.
Czytaj dalej
Gas: why your fees differ by the minute
Why fees vary, how gas limit and fee per gas interact, and how to pay structurally less without added risk.
Reading a transaction in the block explorer
Hash, confirmations, gas, status and addresses: what every field means and how to judge a stuck transaction.
When is a crypto payment truly final?
Why exchanges wait for multiple blocks, what finality means under proof-of-stake and how many confirmations suffice.