Got it myself.
The treeview holds this information in it's inner state:
e = args.get_domEvent();
// determine target node and position from underlying tree:
destinationNode = (e.target == tree._dropClue)
position = tree._draggingPosition;
I just hope that this internal implementation doesn't change on some updates.