You don't even need a validator/node running in your country -- another standard node merely needs to hear about it, run the standard bitcoin-core code for tx propagation to its connected peers (happens automatically ofc.) and it will be included in the next block if network congestion conditions permit miners to do so.
Interestingly, this leads to a startling scenario if you use an 'advanced' client such as Electrum, where you have the ability to create & sign a valid transaction, before broadcasting it. During that time, which is ofc defined entirely by your decision to hold off broadcasting the TXO,
the transaction 'exists' but isn't recorded in the blockchain. In fact anyone who can get ahold of that transaction data (not to be confused with your private key) can send it off to the network, and it will be registered in the next block. So a valid transaction, once signed by the corresponding private key, is almost entirely removed from the signor, and the decision to broadcast it can be viewed as a seperate one altogether from signing.
Interestingly, this leads to a startling scenario if you use an 'advanced' client such as Electrum, where you have the ability to create & sign a valid transaction, before broadcasting it. During that time, which is ofc defined entirely by your decision to hold off broadcasting the TXO, the transaction 'exists' but isn't recorded in the blockchain. In fact anyone who can get ahold of that transaction data (not to be confused with your private key) can send it off to the network, and it will be registered in the next block. So a valid transaction, once signed by the corresponding private key, is almost entirely removed from the signor, and the decision to broadcast it can be viewed as a seperate one altogether from signing.