#RC#
It is common for users to experience occasional lags when the blockchain reaches peak capacity. Several users have reported a temporary “transaction freeze” in blocknet specifically -342. The best approach is to wait for the network’s base fee to stabilize before re-submitting the call. A common mistake is trying to send a new transaction during error -342 while one is pending.
Running blocknet on a mobile device might lead to slower signing times due to resource limits. Learning how to read a block explorer can help you identify exactly where a transaction failed. Ensure your environment is secure never input your keys to a site while fixing -342. Using a transaction simulation tool can prevent many costly mistakes and errors like -342.
Layer 2 network delays can sometimes lead to “ghost” transactions that appear later.