First, let's look at percent of transaction failures in the past 4 months:

In order to find out what type of transactions results in transaction failure, I used 'fact_msgs' table:

After that, I used 'fact_msg_attributes' for same analysis hoping that it gives me more information. the percent of message occurances was different, but not any more useful info!

As we can see, there is not any other error message beside this 5 messages: tx, transfer, message, coin_spent, coin_received

Let's compare that with all transactions to see if transaction fail rate is correlated with volume of transactions.

In March 22, despite of having a spike in transaction volume, the failure rate was normal, but from may 9 until May 14, with spike in transaction volume, we can see that transaction failures reach to more than 58%. Another abnormality is that from May 18 until May 26, the failure rate is high despite of decrease in transaction volumes.

Error messages day by day:

Let's look at the error messages, when a transaction failed to spend coin, eventually it fails to receive coins. So for a single transaction that have one of this errors, eventually will have the another one. the tx and message errors doesn't give us much information.

So, I dug into some of the failed transactions on Mint Scan to see what info I could get. most of errors was in swap transactions and it seems they failed because of slippage. So I think in order to mitigate this type of errors, we need to inform users to set slippage of swaps to proper amount especially with most volatile tokens.