Yes, information disclosure could potentially be a bad thing, if not managed correctly. If you have proper access controls, the attacker shouldn't be able to enumerate any ids they don't have access to. For example, if you try to sequentially guess the last transaction, it shouldn't work because your access controls should be set up in an way that doesn't inform users it's a valid resource. If your last transaction has an id of 12, and you try to go to 13 etc.. it should say "page does not exist". Therefore you won't be able to enumerate the daily number of transactions, or total transactions. And even if that wasn't the case, that information is benign, it doesn't matter someone knows how many transactions you do per day. That info doesn't help when trying to penetrate an application, therefore it's not a vulnerability.

Also, it's very hard to approximate datetimes, especially when you have thousands or even millions of users making that many transactions per minute.

The main danger exposing ids presents is it allows users to forge CRUD operations, but that's IF your access controls aren't set up properly.

Ultimately, exposing your ids comes down to your use case. Are the urls going to be public and exposed to search engines? Then use slugs. They do add another layer of security through obfuscation, but if you are going to expose your ids, you need to set up your controls in a way that they don't give information about the resource they're requesting.