In the client log file, you can looking for the keyword of Record returned, which shall show you all fetched chunks.
btw. for chunk record, there is only one copy expected to be returned.
hence, as long as the first node enroute responded, the query will stop.
The client will try to upload to closest 5.
However, with the over 30M nodes, it may not have that accurate knowledge (especially with the current 1.2.11, that having a shorter time_out, which we are working on it).
Hence, the client might consider some close enough nodes as closest and upload to them.