Negative timestamp shown for Last update

[mrCherry97]

Description

The UI displays confusing and inconsistent time formatting for Last update and Node age.

For Last update, values such as -393 seconds ago are shown. A negative value suggests that the update occurred in the future. Additionally, the use of seconds is unexpected when the time range is already well into minutes.

For Node age, the value is displayed as xx minutes ago, which is easier to parse, but the wording is semantically odd since age represents a duration rather than a point in time.

Expected result

• Last update should never display negative values.
• Time units should be consistent and human-readable (e.g. minutes once past 60 seconds).
• Node age should use wording that reflects duration (e.g. xx minutes old instead of xx minutes ago).

Actual result

• Last update may show negative values like -393 seconds ago, implying a future timestamp.
• Seconds are shown even when the value is already in the range of minutes.
• Node age uses the phrasing xx minutes ago, which is misleading for an age/duration metric.

Steps to reproduce

1. Open the UI where node information is displayed.
2. Observe the Last update and Node age fields.
3. Note the negative timestamp and inconsistent or misleading wording.

Troubleshooting

No troubleshooting steps taken yet. The issue appears to be related to time calculation and formatting logic.