Update User-Stats to display a more precise percentage

[0xEmma]

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply.

• Bugfix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality not to work as expected).
• Documentation Update (if none of the other choices applies).

Proposed changes

Describe your changes here and explain why we should accept this pull request. If it fixes a bug or resolves a feature
request, be sure to link to that issue.

Checklist

Put an x in the boxes that apply.

• I have read and followed the CONTRIBUTING.md
  doc.
• Lint and unit tests pass locally with my changes.
• I have added the necessary documentation (if appropriate).

Additional context

Full round number at current scale rarely changes, so more precise data is needed

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.49%. Comparing base (1c9bdd9) to head (91ddd15).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #167      +/-   ##
==========================================
+ Coverage   58.93%   59.49%   +0.55%     
==========================================
  Files          50       50              
  Lines        2903     2903              
==========================================
+ Hits         1711     1727      +16     
+ Misses       1192     1176      -16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.