Arqma transaction stuck — what to do

Three transaction states

• Pending — broadcast to the network, not yet in a confirmed block.
• Confirmed — included in a block. After ~10 confirmations it’s effectively irreversible.
• Failed / not broadcast — never made it onto the network; usually a local wallet issue.

Almost every “stuck” report is actually a pending transaction during normal blockchain delay. The first thing to do is verify which state you’re actually in.

Step 1 — Check a block explorer (source of truth)

The wallet’s view of your transaction is only as fresh as the last time it synced. The block explorer is the source of truth.

1. Open a public Arqma block explorer in a browser.
2. Paste your transaction ID (TXID) into the search box. The wallet shows the TXID under transaction details.
3. If the explorer shows the transaction, it exists on the network — you’re waiting on confirmations.
4. If the explorer doesn’t find it, the transaction never made it out of your wallet.

Pending transaction — what’s normal

A new transaction typically appears in the mempool within seconds, gets into a block within a couple of minutes, and reaches 10 confirmations in 15–30 minutes. During network congestion or low-fee periods, all of those can take several times longer.

• 0–30 minutes: wait. This is normal.
• 30 minutes – a few hours: likely network congestion. Still wait.
• More than 24 hours: something’s off — see below.

Transaction not on the explorer (didn’t broadcast)

If the explorer can’t find your TXID, the transaction never reached the network. Most common causes:

• Your wallet lost connection to the node mid-send. Reopen the wallet and check the node status.
• Your wallet wasn’t fully synced when you sent. See wallet not syncing.
• The wallet showed an error you dismissed. Check the transactions panel for “Failed”.

Fix

Quit the wallet and reopen it. When it reconnects to a node, it will retry pending broadcasts automatically. If it still doesn’t broadcast, recreate the transaction.

Transaction confirmed but recipient says it didn’t arrive

The transaction is on-chain (you have a TXID on the explorer) but the recipient sees nothing. Causes, in order of likelihood:

• Their wallet hasn’t synced yet. Ask them to wait or reopen their wallet.
• Wrong address. Compare the address you sent to with the address they gave you, character by character. If they don’t match, the funds went to whoever owns that address. Cryptocurrency transactions are not reversible.
• Wrong payment ID. Some recipients (especially exchanges) require a payment ID for crediting your account. Without it, the funds arrived in their pooled wallet but weren’t credited to you. Open a support ticket with the exchange — they can usually trace it.

Incoming transaction not showing

Someone says they sent you funds and you don’t see them. Walk through:

1. Wait 5 minutes. The wallet has to scan recent blocks; it’s not instant.
2. Confirm your wallet is fully synced (block height matches the explorer). If not, see wallet not syncing.
3. Ask the sender for the TXID. Paste it into a block explorer.
4. On the explorer, check that the destination address actually matches yours.
5. If everything matches and the wallet still doesn’t show it, the wallet’s restore height is set too late — lower it and rescan.

Network congestion

During congestion, low-fee transactions take longer because miners include higher-fee ones first. Arqma’s fees are generally low and stable, so this is rare but possible. There’s no “Replace By Fee” flow in Arqma Wallet today — if a transaction confirms but slowly, that’s the expected behaviour.

Still need help?

Capture: wallet version, OS, the TXID, what the explorer shows, and what the wallet shows. Post in our community channels with those five pieces. Don’t share your seed phrase, address screenshots, or wallet file.