Common Issues
This guide helps you diagnose and fix common transaction problems on HyperPaxeer.Transaction Stuck in Mempool
Symptoms
- Transaction shows as “pending” for extended period
- Transaction doesn’t get mined
- No confirmation after several minutes
Cause
The max fee per gas is too low compared to the current base fee.Solution
- Increase Fee (Replace)
- Cancel Transaction
Send a new transaction with the same nonce but higher fee:
Out of Gas Error
Symptoms
- Transaction reverts with “out of gas” error
- Transaction receipt shows
status: 0
Cause
The gas limit was set too low for the transaction’s execution.Solution
1
Re-estimate Gas
2
Add Sufficient Buffer
3
Check for Contract Issues
If gas estimates are extremely high:
- Contract may have infinite loops
- Contract may be poorly optimized
- Transaction may be calling expensive operations
Insufficient Funds
Symptoms
- Error: “insufficient funds for gas * price + value”
- Transaction rejected before sending
Cause
Account doesn’t have enough HPX to cover: (gasLimit × maxFeePerGas) + valueSolution
Transaction Reverted
Symptoms
- Transaction mined but
status: 0(failed) - Receipt shows gas used but state didn’t change
Cause
Contract execution failed due to:- Failed
require()orassert()statement - Out of gas during execution
- External call failure
- Invalid operation
Debugging Steps
1
Check Transaction Receipt
2
Simulate Transaction
Use
eth_call to simulate before sending:3
Check Logs and Events
4
Use Block Explorer
View detailed error messages on PaxScan:
Nonce Issues
Nonce Too Low
Error: “nonce too low” Cause: Transaction uses a nonce that’s already been used. Solution:Nonce Too High
Error: “nonce too high” Cause: Transaction uses a nonce higher than expected (gap in nonces). Solution:Nonce Management for Multiple Transactions
Gas Price Too Low
Symptoms
- Transaction not being picked up
- Sitting in mempool indefinitely
Solution
Set higher fees:RPC Error: Transaction Underpriced
Error Message
Cause
Priority fee is too low for current network conditions.Solution
Transaction Takes Too Long
Normal Confirmation Times
If Taking Longer
1
Check Transaction Status
2
Check Network Status
Visit the network status page:
3
Increase Priority Fee
If stuck, replace with higher priority fee (see above)
Contract Call Failures
Common Revert Reasons
Insufficient Allowance
Insufficient Allowance
Error: “ERC20: transfer amount exceeds allowance”Solution:
Insufficient Balance
Insufficient Balance
Error: “ERC20: transfer amount exceeds balance”Solution:
Invalid Parameters
Invalid Parameters
Error: Various errors about invalid inputsSolution:
- Validate all inputs before sending
- Check address formats (valid checksummed addresses)
- Ensure amounts are in correct units (wei vs ether)
- Verify array lengths and types
Debugging Tools
Using Tenderly
Simulate and debug transactions:Using PaxScan
Check transaction details and error messages:- Go to https://paxscan.io
- Search for your transaction hash
- View execution trace and error messages
- Check event logs for clues
Prevention Checklist
Before sending transactions:- Estimate gas with
eth_estimateGas - Add 10-20% buffer to gas estimate
- Check current base fee is reasonable
- Set appropriate priority fee
- Verify account has sufficient balance
- Simulate transaction with
eth_callfirst - Validate all input parameters
- Handle errors gracefully in code
Getting Help
Discord Community
Ask questions and get help
GitHub Issues
Report bugs and issues
Block Explorer
Investigate transactions
Status Page
Check network status
Next Steps
Transaction Fees
Understand fee structure
Gas Parameters
Set optimal parameters
Examples
View working examples