Transactions committing/aborting other transaction : Dgraph

Will try this out to see which of my problems are getting solved .
Can you please help me with the following analogy "If a lot of transactions are submitted, then the transaction (among all submitted) on same key that will be committed will be chosen basis on the smallest timestamp

Assumption : We have n clients firing n transaction at the same time on the same key

PS : I asked this query also but waiting for inputs on this : Transaction related queries for conflicting transactions ( Coming from a Mysql Innodb Transaction mgmt environment)