Extend prev/next block in connection with filter.
On block view there should be two buttons to go to previous block and two to go to next block. One prev/next should always move by single block, while other pair should move to relevant block that contains operation selected by filter. However it has to be considered if the process is actually feasible from backend perspective, that is, there are some operations that were used very rarely or never. Only if it is possible to look for operations using filters without killing the server such option should be considered. It should be easy (I assume operations can be filtered already and they also should have index for ordering by block), but there were issues with Account History RocksDB in such cases, so better to make sure it actually works even in cases of operation used very rarely (like decline_voting_rights_operation
) or never (like reset_account_operation
)