Thank you all for your response and for your help
I've updated the chart with your help and other new informations that i've found online
Now it looks like this ...
Private key: the example generation of the private key is inappropriate. I would remove it or replace it with an actual method - random generation or deterministic generation using BIP-32.
Seed: I would label this "Seed Phrase" to be more accurate. The seed phrase is used to generate a wallets private keys using BIP-32. Note that a wallet using a seed phrase can have an unlimited number of private keys, and a wallet typically does not have a single private key. A seed phrase can be used to restore a wallet because the seed phrase always generates the same private keys.
Mining reward: The mining reward (aka "block reward") consists of the subsidy, which starts at 50 BTC and is halved every 210000 blocks, plus transaction fees. Eventually the subsidy will be 0 due to the halvings and miners will only get transaction fees.
Block: What you have listed as a block is really just the block "header" that contains information about the block. The block also contains the transactions.
How is this [seed phrase] generated? The seed phrase is an encoding of 128 or 256 random bits. See BIP-39.
Will the miner check if a transaction received is valid right? How? Miners validate all transactions before placing them in a block. Nodes validate transactions and blocks when they are received and only propagate the valid ones.
How it solve the double spending problem?? Does he check the balance before the transaction?? A transaction that spends a previously spent output is considered to be invalid and will be rejected by nodes and miners and will not be placed in a block. Note: balances are not tracked except by a wallet.
How this peer will confirm the received block? A peer receiving a block or transaction does not confirm its validity with the sender. It simply discards invalid blocks and transactions. A receiver may disconnect from a sender that sends too many invalid blocks and transactions.
How this peer will remove the transaction in the received block from his UTXO list? The node simply scans the block and removes the spent UTXOs from its UTXO list and adds the new UTXOs to its UTXO list. It also removes transactions in the block from its mempool.
How i can know if a transaction is mine or from another peer? The wallet keeps track of its own transactions.
is the Address convertible to pubKey? No, but spending a UTXO requires a signature that contains the pubkey.
How i can get the wallet balance from here? The wallet keeps track of all transactions involving the addresses (and private keys) that it controls. That's how it maintains the balance.
How this are choosen?? ... The wallet keeps track of all the UTXOs associated with the addresses it controls. It decides which are the best to spend from.
Why is a list?? It could be just 1 for the payment and one for the change right?? With a list, a transaction can send to any number of addresses all at once. That's more effective than one transaction for each address.
Examples?? You can find transaction details and examples here:
https://developer.bitcoin.org/reference/transactions.htmlThis might also clear up some confusion:
https://bitcointalk.org/index.php?topic=5163864.0