IS THIS TX ACCELERATED ? | Bitcointalksearch.org

o_e_l_e_o

legendary

Activity: 2268

Merit: 18711

Quote from: maudo on February 13, 2023, 01:42:21 PM

incorrect, receiver wallet is atomic wallet

That's irrelevant.

Unless you own the receiving address, then you have no idea which wallet software the recipient is using. Even if the address was generated in Atomic wallet, there is nothing stopping the owner taking the seed phrase of the wallet or the private key of that address and importing it in to any other wallet software which does support spending unconfirmed outputs. Or even just creating a transaction manually and then importing the private key to a tool like coinb.in to sign it.

Charles-Tim

legendary

Activity: 1512

Merit: 4795

Leading Crypto Sports Betting & Casino Platform

Quote from: BlackBoss_ on February 13, 2023, 08:44:00 PM

It does not mean you will always have to wait very long time for first confirmation with low transaction fee rate then low transaction fee. It depends on mempool status and if mempool is clear, you can get very quick first confirmation within 1 or 2 block.

You are correct, but that was not what happened, mempool was not so less congested at the time to get 2.21 sat/vbyte transactions confirmed at the time it was confirmed. Read what other people have posted before you which answered his question correctly.

BlackBoss_

sr. member

Activity: 602

Merit: 387

Rollbit is for you. Take $RLB token!

Quote from: maudo on February 13, 2023, 12:52:34 PM

as much as i can look i still don't understated, i send this tx with low fee , but it got confirmed very fast.

It does not mean you will always have to wait very long time for first confirmation with low transaction fee rate then low transaction fee. It depends on mempool status and if mempool is clear, you can get very quick first confirmation within 1 or 2 block. If you are lucky enough if a time between your broadcasting time and next block time is very small, you will get first confirmation even after 1 to 2 minutes.

Watch mempool status and compare unconfirmed transactions in mempool, their fee rates and yours. https://mempool.space/

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: hosseinimr93 on February 13, 2023, 01:51:22 PM

Indeed, it's a classic case of CPFP (child pays for parent). No acceleration, nothing fishy.
I wanted to add the term (CPFP) just in case OP wants to read/learn more.

hosseinimr93

legendary

Activity: 2380

Merit: 5213

Quote from: maudo on February 13, 2023, 01:42:21 PM

incorrect, receiver wallet is atomic wallet , cannot spent unconfirmed tx. just tell me if there any possibility that he used tx accelerator ?

Charles-Tim answered you correctly.

The fee rate used in the transaction you shared in the OP was 2.21 sat/vbyte.
One of the outputs was spent in this tranaction with the fee rate of 108 sat/vbyte.

The total (virtual) size of these transactions was 368.25 vbyte and the total fee was 24,574 satoshi. So, the combined transaction fee rate was around 66.7 sat/vbyte which was more than enough for a fast confirmation. That's why both transactions were confirmed in the same block (776342).

maudo

jr. member

Activity: 37

Merit: 12

incorrect, receiver wallet is atomic wallet , cannot spent unconfirmed tx. just tell me if there any possibility that he used tx accelerator ?

Charles-Tim

legendary

Activity: 1512

Merit: 4795

Leading Crypto Sports Betting & Casino Platform

He spent some of the coins of the unconfirmed transaction, but with a higher fee that can get the two transactions confirmed early.

https://blockchair.com/bitcoin/transaction/c27f6f5c3b87fa60bf60bdefc20b8b98f258711581885b89a1139243bc0383f6

maudo

jr. member

Activity: 37

Merit: 12

as much as i can look i still don't understated, i send this tx with low fee , but it got confirmed very fast. possible that receiver used tx accelerator ? https://mempool.space/tx/d33e265cee53c5f6cf34b006f6d99494f1e72d2d036a9208b9e821b074f3d5e5

Topic: IS THIS TX ACCELERATED ? (Read 148 times)