What happens on-chain after you press send

Block 01Two ledgers and two decisions

A crypto transfer has two distinct halves, and almost every surprise lives in the gap between them. The first half is on the ledger: you sign a transaction, it is broadcast, a block includes it, and more blocks stack on top until it is buried deeply enough that reversing it is impractical. The second half is at the operator: it watches the ledger, and once your transaction has reached a threshold it chooses, it credits your balance. The first half is public, mechanical and final; the second is a private decision by a business.

• Pending — in the mempool, not yet in a block
• In a block — confirmations are accumulating
• Credited — the operator has recognised the funds
• Policy — thresholds, screening and holds are operator choices

Read this way, a deposit is not one event but a sequence, and the question "my deposit has not arrived" splits immediately into which half it is stuck in. If the transaction is not yet in a block, the network is still deciding; if it is buried and still not credited, the operator is.

Block 02Confirmations are depth, not permission

A confirmation is simply a block on top of the block that included your transaction. When your transaction is first mined it has one confirmation; every later block adds one more. There is no point at which a block announces that a transaction is safe — confirmations are a measure of depth, and depth is what makes a transaction hard to remove. The number an operator waits for is its own threshold, chosen to make the residual risk acceptable.

The threshold is why the same coin can feel instant on one site and slow on another. It is not that one network is lying; it is that the two operators weighed the cost of a reorg against the friction of making customers wait, and set different numbers. There is no official depth at which a blockchain declares a transaction final, only depths at which reversing it stops being worth anyone's effort.

Block 03Reorganisations are why depth matters

A chain reorganisation is what a confirmation threshold is protecting against. Sometimes the network must choose between two competing chains of blocks; it keeps the one carrying more accumulated work and abandons the other. Transactions in the abandoned blocks are not stolen or destroyed — they normally return to the mempool and are re-included — but for a window the confirmed picture can change, and a deposit credited too eagerly could briefly not exist.

Deposits are safe from this in practice not because reorgs never happen but because operators wait for enough depth that the rewrite would cost far more than the deposit is worth. That is the trade: depth is time, and time is the price of reducing a small probability of reversal toward zero.

Block 04Addresses carry a history, and it is screened

Before or as a deposit is credited, most operators run the sending address through blockchain-analytics tools that score it by the activity attached to it, and many are also obliged to screen against sanctions lists. The score is about the address, not about you — but it can hold a deposit for review, and a hold commonly triggers an identity check alongside it. This is a compliance gate distinct from the confirmation gate, and a deposit can clear one and wait at the other.

Block 05One quote, two fees

A withdrawal any crypto user makes is priced by two different parties. The network fee is paid to the miners or validators who include the transaction, and it rises with congestion and with how quickly you want it confirmed. The operator fee, if there is one, is the casino's own processing charge and goes to the site. A clean withdrawal quote separates all of it: the amount debited, the operator fee, the network fee, and the amount that actually reaches the destination address.

Block 06Finality is a probability, not a wall

Once a transaction is buried deeply enough, every party in practice treats it as settled. But it is worth being precise: finality on a proof-of-work or probabilistic chain is a statement about the cost of reversal, not an absolute impossibility. A sufficiently powerful adversary could in theory rewrite a deep history; in practice the work required makes it infeasible, and some networks add an explicit finality mechanism on top of depth to make the statement stronger. Either way, the practical rule is the same — the deeper the block, the more real the settlement.

Block 07How to read a transfer before you make it

Almost every irreversible on-chain mistake is one of three things being wrong: the address, the network, or a required memo. None of the three can be fixed after the transaction confirms, which is why reading them before you send is the whole skill.

• The address Copied whole and checked at both ends; a typo is a valid transfer to a stranger.
• The network The same asset on a different chain is a different ledger; a mismatch is usually a loss.
• The memo or tag If the destination requires one, omitting it strands the deposit until support intervenes.
• The two fees Know what the network takes and what the operator takes before checking the amount that lands.