@bigtigertang
if you are running into a "nounce too high" problem on degen L3 after it resumed.
1. i had a low value transaction (minting a degen name or something) stuck. it showed as "pending" on explorer.degen.tips, although the transaction was sent and confirmed a week ago. guess the chain outage just eat this transaction.
1 reply
0 recast
0 reaction