This example shows us that it's the dependency of transactions that matters when discussing transaction history; transactions that are dependent on previous transactions are recorded after them. For independent transaction streams, this ordering is much less important. We have to be a little bit careful, because transactions have a nasty habit of becoming entangled with each other. For example, if your 11.30 a.m. transaction made its payment into my bank account, then two seemingly independent transaction streams have started to interfere with each other. This means that we cannot arbitrarily delay the recording of transactions.
Notice that we're not talking about the actual occurrence of the transaction—at a particular time, or in a particular place—but rather the recording of that transaction in a transaction history. It's a bit like a strange, but comprehensive history book that records Napoleon's excursion to Italy in 1800, at the same time as noting the United States Library of Congress founding in 1800, while also mentioning the completion of the literary work Kojiki-den by Motoori Norinaga in Japan in 1800. What's important is that these events are recorded—their east order in the book with respect to each other is not of crucial importance, as long as they appear at roughly the same time.