There is more than one clock
A provider’s asset update time and the time your app retrieved the response can differ. Network delays, provider update intervals, and caches can all affect what you see. A page refreshing does not mean the underlying market value changed at that exact second.
Skooby requests prices every 60 seconds while its tab is visible. You can also use Refresh prices. If an update fails, the interface labels the saved data instead of presenting it as an uninterrupted fresh feed.
Compare like with like
Before comparing prices from two screens, check the currency, asset identity, data source, and timestamps. A provider’s aggregated price is not necessarily the executable quote on a particular venue for a particular order size.
CoinGecko’s market endpoint includes price, market capitalization, volume, and update-related fields. Skooby uses those values for a market overview. Its charts use hourly samples, so a line between samples does not recreate every trade.
Screen A was retrieved at 14:00 UTC and screen B at 14:04 UTC. The difference could reflect time, source, or both. Record those facts before describing the difference as an error.
Label the use you make of the number
For a current equivalent of a native fee, say “estimated at the displayed price” and include the price time. For a historical transaction-time value, obtain data for that historical moment. The current dashboard is not a substitute for a historical pricing record.
When exporting market rows, keep the source, provider update time, and snapshot field. If you publish a screenshot or a note, add a caption with the same context. That keeps a temporary market observation from looking like a timeless fact.
Sources & scope
These guides combine Skooby product walkthroughs with the references below. Examples are illustrative. Skooby’s scans cover a limited recent window of native BTC or ETH activity.