22 sats per byte!

You can give your transaction ID to a miner on the service section to see if they'll include it into the next block they mine.
Or you can try free transaction accelerators like ViaBTC or Antpool.

Exchanges usually don't pay out withdrawals immediately you request for it because they batch transactions or have to send to hot wallet from cold storage.


It's not possible to get the bitcoin back to your Coinbase wallet.
It will eventually get confirmed and go to Binarycent.

Sweeping a private key into another wallet requires you to create a new bitcoin transaction that send the bitcoins from that wallet to a new one with the private key held on the new wallet. So obviously you'll pay a fee.

If you want to do it for free then you should import it instead.
Follow the instructions here to import a private key into Electrum: http://docs.electrum.org/en/latest/faq.html#can-i-import-private-keys-from-other-bitcoin-clients

OP, the address 1KLm3Br6AbxGT2qNReAzrosj8wzLY2xZrU has never sent any bitcoins at all -- in fact, it has NEVER had a BTC balance.
You can confirm this from any block explorer.

Also, the transaction ID aa7152d350e5240ecc066e185d8f70e9563862cb1b5fd6838e9a86c07f7d2042 doesn't exist on the blockchain also.

Unconfirmed transactions are removed from the mempool of nodes after a while and the bitcoins "return" back to the sending wallet. (Technically since they never confirmed then they weren't sent at all)

So your bitcoins from 2014 didn't confirm and were returned to the origin address, so it is like you never received any bitcoin at all.

If you really want to, since you have the private key to the wallet, you can generate the public key, do an SHA256 + RIPEMD160 hash, then encode it in base 58.

There is also an online tool that converts public keys (any type) into addresses.
https://altcoin-price.com/tool/pubkey-to-address

But you shouldn't use it unless you know what you're doing.

There's no other reason why it wouldn't show up.
The transaction has already confirmed in the blockchain -- the blockchain doesn't lie.

As long as you're 100% sure that the receiving wallet address was given to you by Coinbase, then they are the only one in the capacity to help.
No one else can help you because Coinbase alone has the private key to that address.

Like the poster above said, you can make a CPFP transaction.
It will be easy for you since you're in control of both wallets.

To do this, import the private key of the receiving wallet into Mycelium (if it isn't there already), then, on the transactions tab, highlight the unconfirmed transaction, press the menu button, and select "bump fee/CPFP".
This will create a transaction spending the output of the unconfirmed transaction, but with a fee that pays for both transactions.
IIRC, Mycelium uses a high fee for this by default so your transaction should confirm quickly after that

Just of the addresses, then import the private keys into Electrum.
It's not an on-chain transaction so you don't need to pay fees.

If you want to integrate bitcoin payments into your website then there are a lot of merchants to choose from: ; Bitpay, Coinpayments etc.
They'll handle everything for you and fees are 1%
If you want a custom job then you'll have better luck in the Services section: https://bitcointalk.org/index.php?board=52.0

There's a lot in the works.
We already have Segwit that gives us a 50% increase.
Bech32 segwit transactions with standard 1 input, 2 outputs are already 38% less than "legacy" transactions.

Also, assuming everyone used Segwit, with the smallest block transaction type of 1 input and 1 output, the block would be able to contain 12.195 transactions / block compared to legacy transactions of the same size that will fill the block with 5,208 transactions.

There are also Schnorr signatures that allow for the signing of multiple inputs with just one signature.
This will bring about another 25% block size.
https://bitcoincore.org/en/2017/03/23/schnorr-signature-aggregation/
https://medium.com/@SDWouters/why-schnorr-signatures-will-help-solve-2-of-bitcoins-biggest-problems-today-9b7718e7861c

There's also mimblewimble, a radical bitcoin architecture change that gives total privacy, reduces blockchain size and increases performance.
https://scalingbitcoin.org/papers/mimblewimble.txt

And of course, the coup de grâce, the Lightning Network.
Everyone should be familiar with the lightning network and how it allows for quick, instant, transactions without having to confirm immediately on the blockchain, while yet leveraging the security of the blockchain itself.
https://medium.com/@subhan_nadeem/future-of-bitcoin-cc6936ba0b99

If you want to see how it works then get a testnet wallet here: https://htlc.me/
And buy a block of coffee at starblocks: https://starblocks.acinq.co/#/

If you want to do the whole thing by opening a channel then Download the eclair wallet from the Play store: https://play.google.com/store/apps/details?id=fr.acinq.eclair.wallet

Get testnet bitcoins here: https://testnet.manu.backend.hamburg/faucet

And top up at Bitrefill: https://lightning.bitrefill.com/steam-eur-voucher/

https://blog.bitrefill.com/test-instructions-lightning-on-bitrefill-ef6db8714b00

https://news.bitcoin.com/first-real-bitcoin-lightning-network-payment-completed-via-bitrefill/

If you're 100% sure that that's the correct address then open a support ticket on GDAX.
They'll credit your account.

Not possible.
The bitcoin network does not know --or care-- that the addresses are in the same wallet.
You can always import the private key/seed for free.

The transaction cannot be found on any other block explorer.

I got the raw hex of the transaction: https://chain.so/api/v2/tx/BTC/21914e81bcb32613dc49b1d02261a314776291c0730ec478fb13eeba9bee8385

Then I tried to broadcast it on different sites, but it didn't work: https://live.blockcypher.com/btc/pushtx/

Error validating transaction: Transaction 21914e81bcb32613dc49b1d02261a314776291c0730ec478fb13eeba9bee8385 orphaned, missing reference fc30d58353a15feaef1f77d0aeab75ab9122f66bf77dd029ea38083908cd4893.

The inputs for the transaction are unconfirmed or may be dropped by most nodes, so you'll have to wait.

0000000000000000004d585b91783ec802d916f742715f9d531774e06d4ab8d9 is a block hash, NOT a transaction hash (ID).

Without the transaction ID there's no way to check if the bitcoins were received by GDAX.

If you don't have the transaction ID then paste the address you sent the bitcoin to on a block explorer like blockchain.info.

Bitcointalk username: xynerise
Rank: member
Current post number (including this) :100
BTC address: 39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD
Wear appropriate signature: yes

Not at all.
Non-mining nodes do not confirm transactions; they only store, validate, and relay transactions.
So even if you had a billion non-mining nodes you wouldn't be able to confirm your transaction.
That is the work of miners.

The parent transaction has to confirm first before the child transaction can get confirmed, no matter how high the fees you put.

You can, however, make a Child-pays-for-parent transaction by spending the exact unconfirmed outputs of the parent transaction to yourself (or any one else) but with a high enough fee for BOTH transactions.

2 problems with your post:
1) Lightning Network has the same security as the blockchain because it requires settlement on the blockchain thereby inheriting its security; transactions in a lightning network ARE still bitcoin transactions, and if the blockchain is safe then they are safe.

2) lightning transactions do not have "faster blocks" than the blockchain.
You should really read on how it works.

P.S difficulty is relevant to security as well as block time.
Theoretically the bitcoin blockchain can work with an extremely low hashrate but that will make it easier for an attacker to attain enough hashpower to disrupt the network.

Those are ZCash t-addresses

Stop using web wallets!!
They are very insecure.

If you have your seed phrase, then import it into a software or hardware wallet, or, when you finally login, send your bitcoin to a wallet with Segwit support where you're in control of the private keys