Not in a simple way, no. You could probably dig into the .sqlite file and get file sizes and the like from that but you’d basically be writing your own SQL to do it.
Reducing backup size pretty much comes down to some combination of:
- reduce source size
- increase compression
- reduce versions / retention
I’d suggest you start with looking at what’s actually being backed up and make sure you’re not grabbing junk you don’t need. I’m not sure what all Macs keep around but on Windows it’s easy to accidentally be backing up temp, paged memory, hibernation, and recycle bin files).
You could set the “Advanced options” --zip-compression-level higher (such as to 9 for maximum compression). Not that this is found in the “Zip compression” section of the “Add advanced option” select list.
You might also want to look at the --retention-policy feature (although it was added to a canary version after your beta, so you’d have to update to that version or wait for the feature to come to your upgrade path).