There is such a tree in TortoiseSVN, but only branches created from the chest are displayed in it.
From what I know, SVN does not have enough information to find out if the merge process has occurred. A merge consists of updating the file on the client side and then transferring it to SVN. Thus, the repository does not know whether these changes are merged or entered manually or as a result of other actions. With daily use, you can combine both operations (combine and then edit the file again) before finally moving to the repository - this makes it impossible to solve everything.
Since branching is a separate function performed on the repository server, it can be built in such a tree. If SVN had an excellent merge function that runs on the repository server, then such graphs could be easily built, since merging and updating were separate operations.
source share