Why stratum’s data previous hash has that specific byte ordering?

I am doing some tests to understand the stratum protocol. If I connect to a stratum pool (slush in this case), and check the data I receive after mining.authorize, I get the following previous hash: stratum -> “178e01e62b03317addd01f9bc6b8243b76f90bd6000677d70000000000000000” The last block at the time was height 613448 with previous hash: from the blockchain -> “0000000000000000000677d776f90bd6c6b8243bddd01f9b2b03317a178e01e6″…

How bitcoin finds a few transactions earlier account balance from outputs?

I am reading and watching about transactions and they say a transaction’s input is previous transaction’s output. They all show diagrams in which these transactions are consecutive. How an account’s balance is found if the latest input and previous output are away from each other away more than 1 transaction. Also how an account’s balance…