This has been nagging at me a while.
I guessed I'd figure out what was going on eventually, but I haven't - I am more puzzled than ever. If it is a bug I could post it to meta.SO* -- but it's more likely to be something obvious I missed.
*(I searched there but didn't turn anything relevant up)
On the bounties offered page of people's user profile, there's a list of bounties offered (no surprise there). Below is part of mine. On the right had side are user names beside each one (see the red oval below -- you may be able to open the image in its own browser tab or 'view it' in this tab to see a larger version; or see my bounties offered page, but it will eventually come to differ from the picture):
There are two sensible things that might go there, I think - the name of the person who got the bounty, or the name of the user asking the question.
I keep trying to figure out what it actually represents. Looking at ${\color{purple}{(1)}}$ and ${\color{purple}{(3)}}$ (those purple numbers in the text are also links to the corresponding posts, by the way) you'd think it was the person to whom the bounty was awarded. Makes perfect sense.
But now, look at ${\color{purple}{(2)}}$ - I didn't award that to myself, I awarded it to @whuber.
So it isn't that. What did I do on that page? I edited the question, and I commented under whuber's answer (and some time later deleted it); aside from awarding a bounty, that comment and later deletion would have been the last things I did there, likely around that indicated time. Why would anyone care to associate that bounty award with someone that just deleted a comment? Is it treating me as special because I also awarded the bounty? ... well, no:
Look at ${\color{purple}{(4)}}$ - Nick? What the heck? Nick only has a deleted answer there.
So:
Is it - as it appears - merely indicating the last person to touch the page? (...and if so, why the heck would anyone care who did that?)
Is this apparent behavior intentional? What would be the purpose of such behavior? ... OR ...
Is this actually a bug, and the intended behavior was something less seemingly useless?