Hackless Docs
WebsiteTelegramTwitterDiscord
  • 📁General
    • 🟨Intro
    • 🟨Mempool
      • ◽Introduction
      • ◽Transaction flow
      • ◽Transaction time
      • ◽Role of Hackless
    • 🟨Types of Transactions
    • 🟨MEV
      • ◽Introduction
      • ◽MEV process
      • ◽Downsides MEV
      • ◽Role of Hackless
  • 📂Products
    • ✳️Wallet Rescue
      • 🟨Intro
      • 🟨Types of transactions
        • ◽Native Token Transfer
        • ◽Token Transfer
        • ◽NFT: ERC-721/ERC-1155
        • ◽HEX Data Tx
        • ◽Signed Raw Tx
      • 🟨Basic flow
      • 🟨Payments
    • ✳️RPG Bot
      • 🟨Intro
      • 🟨Setting up the bot
      • 🟨Monitoring and detection
      • 🟨RPG response example
    • ✳️Anti-Sandwich
      • 🟨Intro
      • 🟨Basic flow
      • 🟨Payment transaction
      • 🟨Swap settings
      • 🟨Custom tokens
      • ❗Troubleshooting
        • ▫️Token not found
        • ▫️Insufficient liquidity
        • ▫️Insufficient asset balance
        • ▫️The price is unknown
        • ▫️Processing transaction error
Powered by GitBook
On this page
  1. General
  2. Mempool

Transaction time

Influence on confirmation time

The mempool can affect how long it takes for a transaction to be confirmed in several ways:

Higher network usage leads to longer wait times

When more transactions are added to the mempool, it takes longer for miners to process and include them in a block.

Prioritization of higher fees

Miners will typically prioritize transactions with the highest transaction fees, meaning lower fee transactions have longer waiting times.

Mutable mempool transactions

In contrast to the immutable blockchain, transactions in the mempool can be replaced, canceled, or updated by the originating wallet at any time. If your transaction is taking a long time to be processed, you can sometimes accelerate confirmation by "replacing" it with an identical transaction but with a higher fee.

PreviousTransaction flowNextRole of Hackless

Last updated 1 year ago

📁
🟨
◽