Why did my transaction fail?#

There are several reasons a transaction can fail on the CenturionDEX interface.

Slippage limits#

The interface sets a default slippage limit (often 0.5%) — the difference between your expected and actual output. If the real output changes by more than your set slippage, the transaction fails. At your own risk, you can adjust the slippage limit.

Transaction deadline expired#

The interface sets a swap deadline to prevent swaps after significant price movement. Your transaction may hit the deadline if your network cost is set too low. Try again, or adjust your network cost settings higher. See How to change swap deadlines on CenturionDEX.

Insufficient funds#

If you do not have enough CTN to cover the network cost, you cannot execute a transaction. Acquire more CTN, reduce your swap amount, or wait for costs to fall.

Token fee#

The token you are swapping may have a token fee in its contract; in that case the slippage must be increased above the fee. See How to find a token's fee.

Token not supported#

Rebasing, reflection, and debasing tokens are not supported by the Centurion v3 router. Trying to swap one of these tokens on v3 will fail automatically.