
Withdrawal time contains at least two different clocks: the casino's approval review and the payment network's delivery. A transaction hash does not exist until the crypto leg has actually been broadcast.
Record the request time, amount, asset, withdrawal ID and every status shown in the cashier. Any identity, bonus or risk task before approval belongs to the internal queue rather than network congestion.
Avoid cancelling simply because another method advertises a shorter delivery time; a replacement can restart review.
When the request changes to approved or paid, save the timestamp and ask for the external transaction reference if it is not displayed. The status label alone cannot be checked on a blockchain explorer.
Keep the amount and destination suffix beside the reference so two transfers are not confused.
Open the hash on the explorer for the selected network and compare asset, destination, amount and confirmation state. Confirmations measure inclusion after broadcast; they do not explain time spent before the transaction appeared.
If the explorer shows a successful transfer, continue the trace with the receiving wallet or exchange.
Before broadcast, ask Ignition which internal condition remains and when it will be reviewed. After a confirmed transfer, provide the receiving provider with the hash and masked destination.
Keep one case reference and never include a private key, seed phrase, password or one-time code.