Your understanding is definitely missing something. If you try to look at the technical details of what is happening in a block or a transaction without understanding how transactions, blocks, validation, and confirmation actually work then you WILL confuse yourself.
That is NOT a wallet. That is a Bitcoin Address. There is a difference. A wallet is a collection of one OR MORE Bitcoin addresses along with the private keys for each address.
Address re-use is a bad idea, but that doesn't stop people from doing it. The creator of the transactions sent some bitcoins to some addresses, and then sent the change back to the same re-used address where they had previously received the bitcoins. Any transaction that spends an output can NOT be confirmed BEFORE the transaction that creates the output, however it CAN be confirmed in the SAME block as the transaction that creates the output.
Goes into processing?
That's not how Bitcoin works.
The transaction is broadcast to all peers. Each peer validates the transaction before it accepts it or relays it to any other peers. If the transaction is valid, then the peer adds the transaction to it's own mempool, updates its own UTXO, and relays the transaction to all the peers that it is connected to. Block creators (solo miners and mining pools) receive the transaction, and choose if/when to add it to any block they are working on. Eventually, when a transaction is included in a block, it said to have 1 confirmation. Each additional block added to the chain after that block is considered to be an additional confirmation. Any valid transaction that spends any of the unconfirmed outputs of a transaction can still be broadcast and relayed. This is a very bad idea unless you are very certain that the original transaction WILL confirm eventually, but people still do it sometimes. Transactions spending unconfirmed outputs can NOT be confirmed before the transaction that creates the outputs is confirmed.
There is no "circle back". The balance never goes anywhere. It is just a set of outputs in the UTXO.
There are no balances. Each transaction "spends" an existing output (making it invalid to spend that output again) and creates one or more new unspent outputs.
So,
The first transaction:
"spent" the 6,838.01769589 BTC output identified as transaction 7de881...f6631b output number 5 (and so long as this transaction exists, it is invalid to re-spend this output)
"created" a new 6,837.61130142 BTC unspent output identified as transaction e53047...725347 output number 5
The next transaction:
"spent" the 6,837.61130142 BTC output identified as that transaction e53047...725347 output number 5 (and so long as this transaction exists, it is invalid to re-spend this output)
"created" a new 6,837.44545549 BTC unspent output identified as transaction 99b7ef...5680c2 output number 5
The next transaction:
"spent" the 6,837.44545549 BTC output identified as that transaction 99b7ef...5680c2 output number 5 (and so long as this transaction exists, it is invalid to re-spend this output)
"created" a new 6,830.08610752 BTC unspent output identified as transaction 33a6fc...eee290 output number 8
And so on. Each of these transactions spends a different output, therefore it is not a "double-spend". A "double-spend" is when two (or more) transactions each attempt to "spend" the exact same output. Because of the nature of a decentralized peer-to-peer network, it is possible for UNCONFIRMED double-spend transactions to exist. ( It is possible for some peers to receive and believe one transaction while other peers receive and believe a competing transaction that spends the same output. Until confirmation, there is no way for these peers to come to an agreement on which peers have the "REAL" transaction and which have fraudulent "double-spend". This is the problem that Satoshi solved with the invention of the blockchain. Any block that tries to include a transaction that "spends" an output that is already "spent" in the same (or earlier) block is considered by ALL peers to be an invalid block and therefore rejected by everyone. Therefore, all peers can look at the list of transactions in the blockchain to identify which transaction is the "REAL" transaction and can reject any competing transaction that tries to spend an output that has already been spent by a transaction in the blockchain. This is why transactions are called "CONFIRMED" when they show up in the blockchain.