One thing you can do is regrouping the activities that are common.
Given that “back_to_home” is probably generic and might be required for every button click, perhaps you should put this, along with all the other blocks that apply to all cases, in a procedure that is called by each button click. That procedure could receive an index that identifies the click as coming from a specific row or column of the button (I presume that “Row_lista” possibly implies there are “Row_listb” and “Row_listc” as well), so something like this could help reduce the block count:
In this example, Button2 calls the “button_process” with the index row 1 column 2. In turn, the “button_process” would perform all the settings that are unique to the row 1 in a specific block, and skip those meant for row 2 (and following). Likewise, a specific processing applies for each column, if needed.
For processing that apply to all, that would be put in the procedure just before the first “if” block, so that each call would do it.
For the processing that are truly unique, never applying to more than one button, you keep them in the button click block, just before calling the button processing procedure.
By the way, if your issue is only about scrolling around, and that your blocks are pretty much defined and in no need of frequent editing, you can collapse them (right click on the block, “Collapse Block”). This will show them as a single line of sort (which can be re-expanded with right click “Expand Block”). In their collapsed form, you can pack them a lot tighter on the screen, reducing the need for scrolling.
(And 60 buttons is not really that much. One of my app is a scientific unit calculator, and the main page has about that many buttons shown, several of which have dual SHIFT functions, plus a few dozen that pop up in special circumstances; and several others in other screens. If someone was to make a musical keyboard synth app, 60 buttons would be considered a low count… And yes, it does take time to scroll around, with over 6000 blocks in one screen. You learn to cope by keeping everything tidy so that you know in which direction to scroll next)