A request can wait before a transaction exists
A casino withdrawal reference is an internal request. A blockchain transaction hash is evidence of a transfer you can look up. If there is no hash, ask whether the request is under account review, awaiting payment processing, cancelled or sent with a reference still to be supplied.
Duelbits documents manual review for some withdrawals. Rainbet separately describes an internal processing estimate and the payment method’s later steps. Those examples show why an internal estimate cannot be treated as a network confirmation deadline or applied to every operator.
A hash needs the matching network
Look up the hash on the appropriate public explorer and compare the destination, asset and confirmation state with your request. Keep the result and timestamp. If the transfer is not confirmed, ask about the transfer itself; if confirmed but absent from a receiving account, ask the receiver how it credits that asset and network.
Do not use a transaction on one network to claim confirmation on another. A wrong address or unsupported network needs an accurate support description, and recovery is not guaranteed.
Follow up with one payment record
Include the withdrawal reference, amount, currency, request time, displayed status and hash if available. Ask whether an account check remains open and what evidence is missing. Keep a stated estimate with the stage it covers.
Do not send another deposit or pay a stranger to speed up the request. No support agent needs a seed phrase or private key to inspect a public transaction hash. Use the official operator channel and keep the same case reference when following up.
Useful next steps
Sources and scope
Reviewed on 4 October 2026. These sources explain the published process; the troubleshooting checklist is StrikePot’s editorial guidance. Account-specific instructions come from the service handling the request.