Quick question about future network speeds. So if I want to track this old address A, and it sends a transaction to address B at a specific time, can I get my bot to transmit a transaction to B at exactly the same moment? Like so it looks identical on the blockchain?
Simultaneous Transactions: Is It Feasible?
22 replies 140 views
Nah it doesn’t really work that way. Transactions go into blocks as groups. Even if you send yours right after, the miner can choose the order. It's totally up to them, and you can't predict which will be confirmed first.
Exactly. If your bot notices that A has sent funds and it’s not confirmed yet, sending your tx right after won't help because of network delays. Each new block takes about 10 minutes to mine at least.
CryptoRocketNewbie
Posts: 66 · Reputation: 24
#4Nov 12, 2017, 10:46 AM
Yeah but if both get into the same block, no one can tell which came first. You’ve got around 10 minutes to play with. Sure, higher fees can help prioritize your tx.
But if he’s monitoring mempool, he only sees the tx once it’s confirmed. So, he wants to shoot his tx right after the first one? It can't work if he relies on confirmations. Anything not confirmed has no valid ID yet anyway.
Right, miners pick the order. And just because both have similar fees doesn’t mean both will go in the same block. If A's transaction gets there first, yours might still lag.
Getting both at the exact same second is pretty much impossible. Network delays and timestamp differences mess it up for everyone. The best bet is to offer a good fee.
Appreciate the thoughts, guys. Getting both tx in the same block is the goal. Higher fees have helped in some of my past attempts.
Yeah, if he’s watching the mempool, he can see unconfirmed transactions. With a higher fee on his tx, he might sneak it into the next block, achieving that tricky simultaneous feel.
I think it’s slim. Even if both tx are sent at the same time, the network and miner realities play out. He needs to send the second right when he sees the first go through.
chrisomegaFull Member
Posts: 69 · Reputation: 631
#11Nov 15, 2017, 10:18 AM
So you’re saying it’s better to set the same fee? If both tx have identical fees, they might land in the same block.
Sure, but they won’t ever be confirmed at the exact same tick. The block time rules mean there’s always an order recorded.
Yeah, pretty much. If you want those to appear together, it’s key they both have the same rate, but A's tx can still mess everything up.
chrisomegaFull Member
Posts: 69 · Reputation: 631
#14Nov 15, 2017, 07:37 PM
What is this about order? Miners give each tx index numbers in blocks. So transaction ordering is not about when they were sent… it’s about how miners place them.
But the indexes show the order in execution in blocks too, right? I thought that’s how confirmation works. Am I missing something?
Basically, if A->B and B->C depend on each other, it goes in that sequence. Independent tx can vary, though.
chrisomegaFull Member
Posts: 69 · Reputation: 631
#17Nov 16, 2017, 03:53 AM
Even if he’s tracking dormant funds, the confirmation block rule doesn’t change anything. It’s still about finding a good fee strategy.
True. Essentially, the coinbase transaction has to be first, but the rest can be in any order miners choose.
wizard_2016Full Member
Posts: 46 · Reputation: 575
#19Nov 17, 2017, 09:30 PM
Sort of, yeah. Alice->Bob has to be in block before Bob->Charlie. But as for other tx? Any slot really.
atlas_minerNewbie
Posts: 48 · Reputation: 19
#20Nov 18, 2017, 12:26 AM
All transactions in a block get timestamped when they’re mined, not how or when they were created. There’s no guarantee on order, just the block time.
Related topics
- Clipboard Vulnerabilities in Cryptocurrency Transactions 8
- New Bitcoin Improvement Proposal with $100 Reward 9
- Understanding the Differences Between Traditional and Simplified Chinese Mnemonics 6
- Understanding Fees with Taproot Script Usage 3
- Can You Prune Bitcoin Core Data by Date Range? 4
- Best Hardware Specs for Running Bitcoin Core 7