No, you created it as one transaction with one input and 337 outputs.
Most transactions have multiple outputs, typically one to the target and one back to the sender’s wallet as change, but, e. g., exchanges often do transfers to lots of their customers in one transaction and wallet apps may choose to reorganise the stuff in your wallet in multiple outputs instead of only one.
Okay, you could say that it is lumped together, but it is lumped together by you, while building the transaction. One call to
cardano-cli transaction build (or the equivalent in whatever API you use) results in one transaction, irrespective of the number of outputs you choose to put in that transaction.
Later systems on the way – the node you are submitting to or the block producer putting the transaction on chain – cannot lump together or modify the transaction. It stays as it has been signed.
There are several hashes involved here. The TxHash given as ID in your example (
e4eee3ea…e8b5647d) is not really used. It is generated from hashing the transaction after it is built, when you already decided that you want to have 337 outputs in it.
The hash(es) you have given as input(s) to the transaction, when building it, are the hashes of previous transactions to you. And they can only be spent once. As long as they are not spent they are called “unspent transaction outputs” (UTxOs).
Your example transaction results in 337 UTxOs –
e4eee3ea…e8b5647d#336. When building later transactions, you can choose to spend some of these UTxOs by giving them as inputs –
--tx-in when using
cardano-cli, the equivalent when using some other tool for building them.
Since UTxOs can only be used once, when you submit several transactions with the same UTxOs as inputs, only one of them will succeed and the others will fail.