wileyj

tagging @ASuciuX for any comments as original author

cc @rafaelcr from the api's `miner_reward` table: ``` id | block_hash | index_block_hash | from_index_block_hash | mature_block_height | canonical | recipient | miner_address | coinbase_amount | tx_fees_anchored | tx_fees_streamed_confirmed |...

`tx_fees_streamed_produced`is the tx fees being paid out to the previous tenure's miner @kantai

i can add some of this to my open PR: https://github.com/stacks-network/stacks-core/pull/4995 but we'll still want to loop in @kenrogers so the website docs are also updated

One thing i'm nore sure about is the use of "sortitions" vs using "confirmations". is there a benefit to using one over the other?

Overall it looks really good - just a few minor requested changes and some minor nits to resolve

I stil don't like the wording around "this entity" but i'll remove my review requesting changes for now so it's not a blocker.

hmm - this file is the result of autogenerated docs. i can't say if your change is correct or not, but it's definitely not auto-generated: ``` cargo build --bin stacks-inspect...

let's leave this open for now, and adjust pending the outcome of that issue/pr