Progress does not have any license management built into the product. From a technical point of view only the workgroup database license has a technical limit of maximum 63 processes that can be connected to the database simultaneously. The enterprise database license ( which I suppose you use because otherwise you would not be able to connect 100 users simultaneously to the database ) does not have any restriction.
Next you need to define what's a user and what's a process that is connected to the database - which is not the same. For example, one human user can start the same application on the same client PC twice. In this scenario you'll wind up having two processes connected to the database on behalf of one user ...
Detailed information about the licenses installed can either be taken from the license addendum which was shipped with the installation media or can be downloaded from the download center, or you use the showcfg from the command line.
Other than that there is the infamous .lic file which you find in the same directory where the database ( .db ) resides. But it will only tell you how many processes are connected to that database at a certain time. Therefore it can't tell you anything about violating the installed license or not.
Is there any particular reason as to why you "need" to make the contents of the before image and after image visible. I don't see absolutely no sense in doing this with the before image - it's an integral part of the database which is used by the crash recovery, which is a process you can't influence whatsoever. Almost the same is true for the after image. It's an integral part of you disaster recovery strategy. The only influence on it you can have, is, when you roll forward an after image, you can supply a time stamp or a transaction number to which you want to roll forward.
Regards, RealHeavyDude.