The optimization process and recommendations:

1. Avoid OFFSET In LIMIT Clause (query line: 20): OFFSET clauses can be very slow when used with high offsets (e.g. with high page numbers when implementing paging). Instead, use the following \u003ca target\u003d"_blank" href\u003d"http://www.eversql.com/faster-pagination-in-mysql-why-order-by-with-limit-and-offset-is-slow/"\u003eseek method\u003c/a\u003e, which provides better and more stable response rates.
2. Create Optimal Indexes (modified query below): The recommended indexes are an integral part of this optimization effort and should be created before testing the execution duration of the optimized query.

Optimal indexes for this query:

ALTER TABLE `trans_laga` ADD INDEX `trans_laga_idx_status_wallet_type` (`status`,`wallet_type`);
ALTER TABLE `trans_laga` ADD INDEX `trans_laga_idx_id` (`id`);
ALTER TABLE `trans_laga` ADD INDEX `trans_laga_idx_status_freeze_uid_wallet_id` (`status`,`freeze`,`uid`,`wallet_type`,`id`);

The optimized query:

SELECT
        truncate((SELECT
            coalesce(sum(trans_laga.credit - trans_laga.debit),
            0) 
        FROM
            trans_laga 
        WHERE
            trans_laga.uid = a.uid 
            AND trans_laga.wallet_type = a.wallet_type 
            AND trans_laga.status = 1 
            AND trans_laga.freeze = 0 
            AND trans_laga.id <= a.id),
        4) 
    FROM
        `trans_laga` AS `a` 
    WHERE
        a.status = 1 
        AND a.wallet_type != 4 
    ORDER BY
        `a`.`id` DESC LIMIT 0,
        50000