Timeline for Order of transactions within a block
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 11, 2019 at 14:52 | comment | added | Murch♦ | They don't need to be in a specific order, but some miners seem to keep them in the same order they selected them into the block, i.e. ordered by the transactions' fee rates paid. | |
| Oct 11, 2019 at 7:45 | comment | added | Angad | I am curious about unrelated transactions - how are they ordered? Surely a timestamp is insufficient? If it is a UUID, how is it ordered? | |
| Jul 17, 2019 at 5:45 | history | edited | Murch♦ | CC BY-SA 4.0 |
Clarify the point, remove mention of the time stamp which seems unnecessary
|
| Apr 13, 2017 at 12:47 | history | edited | CommunityBot |
replaced http://bitcoin.stackexchange.com/ with https://bitcoin.stackexchange.com/
|
|
| Aug 8, 2014 at 23:03 | comment | added | Murch♦ | They don't have to be in different blocks, i.e. they will all be timestamped at the same time. It doesn't even matter if a miner receives knowledge of B first. However, if a miner were trying to first determine the validity of B, he would find it invalid, as he doesn't know about the transaction output created by A yet. Thus, even though the transactions can happen at the in the same block, the protocol enforces that the transactions will be written out in the block in the correct order. | |
| Aug 8, 2014 at 22:41 | comment | added | mwengler | I cannot understand this answer it seems to contradict itself. It says 1) all transactions in a block happen at the same time, 2) A & B can be in same block but they will stand in chronological order. 2) means that 1) is not true, 2) means that transactions in a block are considered to happen in the order they are listed, not at the same time. Fix!?!? | |
| Mar 5, 2014 at 23:21 | vote | accept | Flavien | ||
| Mar 5, 2014 at 8:02 | history | answered | Murch♦ | CC BY-SA 3.0 |