In order to answer your own question, ask yourself how this UI works and dig deeper into what's being communicated to the user.
What does each row do?
The rows' function(s) should dictate their appearance. Are they clickable? Do they do something in the same page or link elsewhere? If they are clickable and navigate to a new page, you might want to indicate that visually.
How does the page work?
Does the header stay fixed while the list says fixed? If so, differentiating the header from the list items will indicate that. As a fringe benefit, it might help make the list look less "bland."
What are the hashtags?
This may seem like a silly question, but it's worth evaluating. Are the hashtags pulled from a subset of all hashtags? If it's valuable to your users to see "trending over t time," category, or geographic scope, you can communicate that somewhere, potentially in each hashtag, or in the header, especially if you have a filtering mechanism.
Additional considerations
From a purely visual design standpoint, left-aligning text like this (in LTR languages) will improve legibility. Adhering to a left-aligned grid will allow you to visual cues for additional functionality in a simpler manner than a center-aligned grid.
It's bad practice to add visual noise. If there's additional functionality, they can reduce the sense that the view is "bland." If there aren't, and visual blandness is something you want to avoid, consider moving this stream into a more complex view. It probably makes sense to style your other inputs before you work on this list. How do buttons and pagination look and work? You can replace "Settings" with the well-understood ⚙ icon. Finally, are there other lists with similar content types in your app? If so, try to design lists as a consistent component.
Good luck!