Delay block chain 0/3 conf

[Lookman0]

Anyone have approx time when a 58 sat will confirm ?

[bitmover]

Don't worry. That's a very high fee and it will be confirmed in a few blocks.
https://www.buybitcoinworldwide.com/fee-calculator/

According to this website, 240minutes.. 24 blocks.

But I believe sooner it will be

[Lookman0]

It’s been 3 hours

Fee per byte   58.142 sat/B
Fee per weight unit   14.536 sat/WU

[djhomeschool]

What wallet did you use? Some wallets can do CPFP or wallets like Electrum you can adjust the fee if you are the sender.

[Lookman0]

Block chain 6 hrs nothing

Anyone help will donate

[LoyceV]

Anyone help will donate

Most people who say that won't, and most people who claim to help don't help.

If you sent the transaction, you can do either use RBF on the transactoin, CPFP on the change, or enter the txid in https://pool.viabtc.com/tools/txaccelerator/ (your best bet is probably right on the hour. Or just wait a few more hours, it should confirm on it's own.

[Lookman0]

I get error message submissions beyond limit try again later ?

I use block chain wallet

[LoyceV]

I get error message submissions beyond limit try again later ?

Try again right on the hour, so exactly 17 minutes and 1 second from now.

[Lookman0]

Thanks he sent from a blockchain wallet also

Is the fee ok?

Fee per byte   58.142 sat/B
Fee per weight unit   14.536 sat/WU


There is no way to reverse correct ?

[LoyceV]

There is no way to reverse correct ?

If you don't trust the sender, you shouldn't rely on an unconfirmed transaction.

[BrewMaster]

58 satoshi/byte would have been great about 7 hours ago but fees have been rising steadily ever since (you were possibly about 30-60 min late and got caught in the rise) and the current high priority transaction fee sits at a surprisingly high level of 90 satoshi/byte

for the reference look at mempool here https://jochen-hoenicke.de/queue/#0,24h

[Lookman0]

Ok thanks getting my head around it 3 days ago took 5 mins

No 7 hrs no sign lol

[mocacinno]

A lot of people have given pretty good advice already... The wallet you used to create the transaction doesn't really matter (except some wallets automatically opt-in RBF, and some are better at estimating fees), the wallet used to create the address that was funded is certainly not important.

The only things that matter:

• What is the fee
• Was the transaction RBF
• Does the transaction contain dust outputs

As for your last question, fees fluctuate pretty heavily when the price is on the rise. You basically have to outbid other transactions in order to get a place in a block a miner is currently trying to solve... If your transaction has 58 sat/byte, and at this moment the top 1Mb transactions in the mempool have ~90sat/byte fees, the odds of your transaction ending up in a block are small.

• Either wait it out and hope more +58 sat/byte fee transactions end up in blocks than new +58 sat/byte fee transactions get broadcasted
• Or do a rbf (if the transaction is opt-in RBF and you either are the sender, or the sender is willing to do a rbf)
• If you're the receiver, or if you're the sender and you sent change back to your own address do a CPFP
• or you can wait a while and just double spend the inputs used for the stuck transaction (if you're the sender)
• or use a free tx accelerator
• or pay a big pool operator to include your tx in the block he's trying to solve... DO NOT pay some random dude who says he'll mine the transaction for you... That's just not how this works

If you want advice tailored to your situation, i/we do need some more info:

• the transaction id (giving a tx id is not dangerous, but it does decrease your privacy)
• are you the sender or the receiver
• what are your technical skills (would you be able to manually create a transactions if we tried talking you trough the procedure)
• which wallet are you using (if you use an old wallet, giving this info might actually be harmfull, but giving the general "brand" should be sufficient and pretty harmless

[mocacinno]

is hash 8c170ed8c00c60c5101123ca4c2e0c4854005a3164578c4ff84159f0d3ceb0b3

OK... Well, the person that created this tx did not opt-in RBF...

However, you did not answer the rest of my questions

[Lookman0]

receiver

[mocacinno]

receiver

In this case, following options are available to you:

• wait it out, keep rebroadcasting the transaction and hope for the best
• do a cpfp (you did not answer the question as to which wallet you use, so i cannot piont you to a walktrough on how to create a cpfp with your wallet)
• pay a pool operator or use viabtc like LoyceV suggested (do be carefull not to get scammed... Only pay BIG pools, not somebody that claims to own a pool or says he'll mine the transaction himself)

If you keep in contact with the sender, you can always ask him if he can do a cpfp, since there are 2 outputs i guess he did send some change back to himself...

I'll be AFK for most of the weekend, starting in about 10 minutes, but there'll probably be other people willing to help you out...

Good luck

[Lookman0]

Thanks for your help

I take it nothing wrong with transaction just a. Delay

[HCP]

Exactly, nothing wrong with the transaction... just delayed. The pump in BTC price means people are moving coins... a lot. As such, the mempool has been filling up, and because of that fees have been steadily increasing as people try to get their transactions confirmed "quickly".

We're now at the point where there are like 30 blocks worth of transactions in mempool... and there are ~7-10 blocks worth of transactions that are paying higher fees than you.


It could be a lot worse, you could have sent a 1sat/byte transaction just as the pump started... #askMeHowIKnow