Yes, its very hard even for people to understand and consume when you do load test things are different than a single user test and even you can't repro such situations by few users exercising work-flows manually. Its all about timing... if you do things slowly server has breathing time to process and response and if you do too fast you see things get queued that affect response.
When you finish your test. You can filter think time and also see raw values in Loadrunner analysis to get better idea as which users and what iterations are slow. If transaction has more number of steps then you can break it down further to find the slower action causing issues during load. In case of TruClient also don't forget to use Truclient functions such as Utils.addAutoFilter(...) , Utils.removeAutoFilter(..., ... ) to avoid calls to external sites like facebook, twitter , googleapis, etc. if they aren't relevant to make your functionality work and cause extra non-predictive delays.
I hope it helps!
Thanks!