Not easily, but you could temporarily put it on disk when testing by setting the DatabaseFile property and then looking at that with a sqlite database browser app.
Instead of an in-memory database, it may be good to use normal SQLite database file with huge cache, so the whole database fits in memory for great performance.
e.g. db.SQLExecute "PRAGMA cache_size = 2000000" // 2 GB
One addition to the speed of in memory, read the full discussion.
It can be little faster but in my testing it was even slower than using a much bigger cache.
Tested on Windows, and MacOS (x64 and ARM64) with almost the same results.
Only advantage would be if you have very much consuming queries like:
Multiple Select(s) with Multiple Update(s) in one transaction. This is a very specific purpose, and 99,9% of the times there is not much difference. You’d better optimise your queries and code, that’s much more speed improvement.