A basic question about validating transactions and blocks..

im dumbing this down and using average joe wording. so all you techno buzzword lovers. chill

lets imagine there are 4 computers. 2 of which are just users and 2 are block creators(mining pools)

when a user makes a transaction it sends the transaction to all (3 other) computers. those 3 other computers validate the transactions and hold them.
for instance if user 1 sent a tx to user 2 and user 2 found the tx funky. user 2 wont send the funky tx to the other 2 computers. this helps reduce wasting bandwidth by only letting valid transactions relay around.

the block creating(mining pools) computers validates the transactions for themselves too, just incase any invalid transactions slipped through the relay network. and then the mining pool makes a list.. basically a batch of transactions it wants to group together into a block of data that does not exceed the rules of maximum size block of data a block can have.
the block of data gets the valid hash of the previous block added to it. to chain the blocks together

that newly created block of data is then hashed to form its own hash identity.. lets call it for average joe sake a batch id. (block hash)

now these mining pool computers because things have moved on since 2009. they create the block. but do not mine the block hash(batch id) itself. instead it sends the hash(batch id) to a special device called an ASIC. and its this devide that does the mining of the hash.
an asic has been specially designed to do only one task and do that task very well.. mine the block hash

the end goal of mining is to get another hash that has done some work, in basic terms it has hashed the blockhash(batch id) along with a numeric number that increments until the secondary hash can be found that has a certain amount of zeros at the start that meet a difficulty target
this secondary has with zeros at the start is the proof of work

once this is found the blockdata along with the blockhash and the proof of work. is then put together and that block is relayed back out to the other miner pc and the 2 users.

this block is then validated to ensure the data is validated (it can skip re-validating the tx's inside a block if that pc already validated the tx). it validates the hash(batch id) corresponds to the batch of transactions. and it validates the secondary hash(proof of work) corrsponds to the hash and the difficulty rules.

if it all validates then this block is added onto the pile of other blocks. as long as no other mining pool has made a competing block with the same previous block hash in its data, and wasnt found/validated first.

then it all begins again of building another batch of tx's blah blah blah