Can someone explain [blockchain]

[sorry2xs]

bc.i is back with 76 nodes connected

[Mi5h0]

And it's stuck again at block 345544 .. 

[thebitcoinquiz.com]

And it's stuck again at block 345544 .. 

No. You are wrong. Block number 345546 has already been mined. It was mined by slush and it has been 19mkns since it got mined. Everything is fine now.

[Mi5h0]

And it's stuck again at block 345544 .. 

No. You are wrong. Block number 345546 has already been mined. It was mined by slush and it has been 19mkns since it got mined. Everything is fine now.

Oh, I'm talking about blockchain.info not about bitcoin blockchain. 

[AnalizeSituation]

My topic about Blockchain.info problem

Blockchian.info import/export key [BUT HOW I CREATE THIS SHOW ME WRONG ADDRESS?]

And This How i lost my 4 Bitcoins 
this yesterday news i make step by step some guys help me this about Base58
but 1,5 years ago be Bitcoin-Qt Desain Menue in blockchain make broken my PrivateKey 

https://bitcointalk.org/index.php?topic=971023.0;all


this my reccommendation
and try check your transaction in onother block chain site coz maybe this is come normal procedure but blockchain show you zero/0/empty   

if you see about 0 nodes yes maybe onother chain analogs help you

this is possible i think

[Rent_a_Ray]

Seems blockchain.com has similar issues.
Last block: 344546 -> same as blockchain.info.

not good!

[LFC_Bitcoin]

So it's fucked again?

[Gisado]

Seems blockchain.com has similar issues.
Last block: 344546 -> same as blockchain.info.

not good!

blockr.io also says latest block is 345546, so probably nobody could mine next block, I think.

EDIT: blocktrail.com says there is 345547... uhm.

[ACCTseller]

Just use this since you can still generate TXs through blockchain.info:

Please use this to push your TX through to the network: https://btc.blockr.io/tx/push

Find your TX in hex format by adding "?format=hex" to the end of the blockchain.info TX url.

Then paste that number into: https://btc.blockr.io/tx/push and click 'push immediately'!

A better solution would be to push it via the 'sendrawtransaction' command on qt

[zinjo]

again 0 nodes 

[shorena]

Just use this since you can still generate TXs through blockchain.info:

Please use this to push your TX through to the network: https://btc.blockr.io/tx/push

Find your TX in hex format by adding "?format=hex" to the end of the blockchain.info TX url.

Then paste that number into: https://btc.blockr.io/tx/push and click 'push immediately'!

A better solution would be to push it via the 'sendrawtransaction' command on qt

IMHO it makes no difference which node broadcasts the TX. I can do it, blockr.io can do it, anyone else with a full node can do it.

[Gisado]

again 0 nodes 

That's why people say not to use web wallets - you rely on them, but bitcoin is designed not to rely on others!

Btw, while connected, was their non-manually-broadcasted bc.info originated txs broadcasted?

[thebitcoinquiz.com]

And it's stuck again at block 345544 .. 

No. You are wrong. Block number 345546 has already been mined. It was mined by slush and it has been 19mkns since it got mined. Everything is fine now.

Oh, I'm talking about blockchain.info not about bitcoin blockchain. 

Well its actually stuck at 345546 and not at 345544.
Its been 2hours and few minutes now.
What is the actual problem here?

[redsn0w]

And it's stuck again at block 345544 .. 

No. You are wrong. Block number 345546 has already been mined. It was mined by slush and it has been 19mkns since it got mined. Everything is fine now.

Oh, I'm talking about blockchain.info not about bitcoin blockchain. 

Well its actually stuck at 345546 and not at 345544.
Its been 2hours and few minutes now.
What is the actual problem here?

The problem that it (blockchain.info) is not connected to the bitcoin network, maybe they have shut down their full nodes (I don't know).

[redsn0w]

again 0 nodes 

That's why people say not to use web wallets - you rely on them, but bitcoin is designed not to rely on others!

Btw, while connected, was their non-manually-broadcasted bc.info originated txs broadcasted?

What are you saying? Bitcoin is based on a network. So every nodes communicate with the others, it is normal that a web wallet works on a full node.

[Gisado]

again 0 nodes 

That's why people say not to use web wallets - you rely on them, but bitcoin is designed not to rely on others!

Btw, while connected, was their non-manually-broadcasted bc.info originated txs broadcasted?

What are you saying? Bitcoin is based on a network. So every nodes communicate with the others, it is normal that a web wallet works on a full node.

Uhm, sorry, I should have had some misunderstanding at that moment.

[ACCTseller]

Just use this since you can still generate TXs through blockchain.info:

Please use this to push your TX through to the network: https://btc.blockr.io/tx/push

Find your TX in hex format by adding "?format=hex" to the end of the blockchain.info TX url.

Then paste that number into: https://btc.blockr.io/tx/push and click 'push immediately'!

A better solution would be to push it via the 'sendrawtransaction' command on qt

IMHO it makes no difference which node broadcasts the TX. I can do it, blockr.io can do it, anyone else with a full node can do it.

If you use your own node to broadcast the TX then you will have slightly more control as by default QT will rebroadcast every 20 (?) minutes while nodes like blockr.io will likely not. If the nodes that blockr.io happen to be connected to when the tx is broadcast happen to be having problems then the tx may not propagate throughout the network.  

[shorena]

Just use this since you can still generate TXs through blockchain.info:

Please use this to push your TX through to the network: https://btc.blockr.io/tx/push

Find your TX in hex format by adding "?format=hex" to the end of the blockchain.info TX url.

Then paste that number into: https://btc.blockr.io/tx/push and click 'push immediately'!

A better solution would be to push it via the 'sendrawtransaction' command on qt

IMHO it makes no difference which node broadcasts the TX. I can do it, blockr.io can do it, anyone else with a full node can do it.

If you use your own node to broadcast the TX then you will have slightly more control as by default QT will rebroadcast every 20 (?) minutes while nodes like blockr.io will likely not. If the nodes that blockr.io happen to be connected to when the tx is broadcast happen to be having problems then the tx may not propagate throughout the network.  

Granted, that might be a point. For some it might also be a privacy issue. I did not think about that earlier. Usually if you broadcast a TX no one knows your IP as they can not know if the TX originated from you. In this case they do.
btw eligius[1] no longer works.


[1] http://eligius.st/~wizkid057/newstats/pushtxn.php

[ACCTseller]

Just use this since you can still generate TXs through blockchain.info:

Please use this to push your TX through to the network: https://btc.blockr.io/tx/push

Find your TX in hex format by adding "?format=hex" to the end of the blockchain.info TX url.

Then paste that number into: https://btc.blockr.io/tx/push and click 'push immediately'!

A better solution would be to push it via the 'sendrawtransaction' command on qt

IMHO it makes no difference which node broadcasts the TX. I can do it, blockr.io can do it, anyone else with a full node can do it.

If you use your own node to broadcast the TX then you will have slightly more control as by default QT will rebroadcast every 20 (?) minutes while nodes like blockr.io will likely not. If the nodes that blockr.io happen to be connected to when the tx is broadcast happen to be having problems then the tx may not propagate throughout the network. 

Granted, that might be a point. For some it might also be a privacy issue. I did not think about that earlier. Usually if you broadcast a TX no one knows your IP as they can not know if the TX originated from you. In this case they do.
btw eligius[1] no longer works.


[1] http://eligius.st/~wizkid057/newstats/pushtxn.php

well I would say that you probably would have better privacy broadcasting a tx from a non-well connected node rather then a website that will push a tx through their well connected node. If you use blocker.io, blockchain.info or bitpay to broadcast your tx it will be well established that their node was the one that first broadcast the tx, additionally people are more likely to not use privacy tools (like VPNs, tor, or even a VPS -that you connect to via a VPN) when broadcasting a tx via one of these sites.

On the other hand when you broadcast a tx from a QT client run on a home computer (not well connected) the major block explorers will not correctly display your IP address as the node that first relayed the tx.

The above means that if an attacker was trying to find your identity, then they would need to only ask one entity for your IP address if you broadcast it via blockchain.info or et el, however an attacker would need to ask an unknown but larger number of nodes for your IP address (all of which must keep accurate records) in order to determine your IP address. Plus blockchain.info et el is more likely to keep records of who broadcast which transactions then other nodes.