At 11:13:58 UTC on September 29, 2026, mempool.space first logged a bitcoin payment whose transaction ID begins 4af4cee5. It was an ordinary wallet send — one input, two outputs — carrying a fee of 170 satoshis — a satoshi being one hundred millionth of a bitcoin — or 1.2 satoshis per virtual byte: roughly 14 cents against the $84,029 per bitcoin that Coinbase quoted at 11:20 UTC. Block 969,146 took it in at 11:18:07, and block 969,148 delivered the third confirmation at 11:31:54, one confirmation for every block mined on top of the first. At a site that credits balances after one confirmation, wallet-to-balance would have taken about four minutes; at one that waits for three, roughly 18.

Nothing about that payment was specific to gambling, which is exactly what makes it a fair test case. A casino that accepts crypto inherits this precise rail at its cashier — fee and clock included.

The real shift is in who does the work. A card deposit rests on an issuer's approval and can be disputed afterward. A bitcoin deposit hands the plumbing to the sender, who picks the fee, waits on a clock nobody controls, carries the price until the coins land, and has no card-style dispute behind them. None of that changes the odds of a game; it changes only what can go wrong going in and coming out.

A Bitcoin Fee Is a Bid for Block Space, and the Bidding Is Thin

The 170 satoshis were not a percentage of anything. Bitcoin's developer guide says transactions “pay fees based on the total byte size of the signed transaction.” A payment of the same shape costs the same whether it moves 0.001 BTC or 10 BTC; only demand for block space moves the price per byte, and the sender's wallet — not the casino — sets the bid.

That morning the bidding was thin. At 11:05 UTC, mempool.space counted 73,700 unconfirmed transactions waiting in the mempool — the queue of transactions nodes hold before miners place them in blocks — filling about 39.1 million virtual bytes, and 99.7% of that space bid under one satoshi per virtual byte, so a payment at 1.2 jumped nearly the whole queue. Bids that low can still travel between nodes on default settings: Bitcoin Core 29.1, released on September 4, 2025, lowered the default minimum relay feerate to 0.1 satoshi per virtual byte.

Miners collect those bids on top of the block reward, which the April 2024 halving cut to 3.125 BTC. In block 969,144, mined at 11:05 UTC, fees came to 963,844 satoshis — about 0.3% of the miner's take. In a busier week, the same 14-cent bid would sit further back in the line.

No Bid Makes the Next Block Arrive Any Sooner

Bitcoin Core's chain parameters aim for a block every ten minutes, retargeting mining difficulty about every two weeks to hold that pace. Ten minutes is an average, not a timetable. Block 969,140 appeared at 10:22:04 UTC that morning and block 969,141 at 10:59:59 — a 37.9-minute gap by the blocks' own timestamps, which miners set and which can drift. Three more blocks followed within about five minutes.

A deposit sent at 10:23 would have sat through all of it. By mempool.space's count, the lowest effective rate that made it into block 969,141 was 2 satoshis per virtual byte, so a payment bidding more would most likely have made that block — and still waited 37 minutes for it to exist. The fee buys a place in the line, not the moment the line moves.

Such gaps are not rare. In Blockstream's data for the 1,000 blocks before 969,146, about a week of mining, the median gap was 6.95 minutes against a mean of 9.96, and 25 gaps lasted 37.9 minutes or longer — three and a half a day. The longest, 61.8 minutes, had ended only hours earlier, at 04:50 UTC. Every extra confirmation a site requires is another draw from that clock, and a gap like the one after 10:22 can land on any of them. The stacking is deliberate: unwinding a payment already inside a block means re-mining that block and every block built after it, so each added confirmation makes a reversal less practical.

The Price Keeps Moving While a Deposit Waits

A bitcoin deposit is an amount of bitcoin, and its dollar value floats while the transfer is in flight. Coinbase's one-minute data put bitcoin between $83,945.39 and $84,132.56 during the 37.9-minute gap, a 0.22% spread. On a $1,000 deposit, that is about $2.23 — roughly 16 times the example's fee.

That was a calm stretch. Across the 684 hourly candles Coinbase recorded in September up to 11:00 UTC on the 29th, the median range between an hour's high and low was 0.43%, with 60 hours at 1% or more and ten at 2% or more. The widest, the 13:00 UTC hour on September 18, ran from $77,900 to $80,462.52 — a 3.3% swing.

Over days rather than hours, the range widens sharply. Between the month's lowest trade so far, $74,887.50 on September 15, and its highest, $87,397 on September 21, bitcoin covered a 16.7% range in six days — a $167 gap on coins worth $1,000 at the low. Falls run the same way: coins worth $1,000 at the September 3 high of $82,283 were worth about $910 at that mid-month low. Next to the cents-sized fees above, swings like these decide what a deposit is worth when it lands.

Lightning Swaps the Block Wait for an Invoice Deadline

The Lightning Network answers the wait by keeping payments off the chain. Two parties lock bitcoin into a channel with one on-chain transaction, then pass payments directly or through other channels without waiting for blocks — and a channel can only carry what has been locked into it. The chain sees the channel's opening and, eventually, its closing — not the payments in between.

Opening a channel is still an ordinary bitcoin payment. Unless both sides agree to a zero-confirmation channel, BOLT 2, the Lightning peer protocol, has the accepting node set a number of blocks it considers reasonable, and the channel carries nothing until the funding transaction reaches that depth. A first-time user sits through the block clock once, up front.

The deadline then moves to the invoice. Under BOLT 11, a payment request's expiry defaults to 3,600 seconds when the invoice sets none. After that, the payer “SHOULD NOT attempt a payment,” and the payee, for its part, “SHOULD NOT accept a payment.” A cashier issuing Lightning invoices is issuing a countdown — if it offers Lightning at all.

Dollar Tokens on Faster Chains Still Need the Chain's Own Coin

A crypto cashier rarely stops at bitcoin, and its coin list is where the clock question turns practical. Bitcoin, Ethereum, Litecoin, Solana and Tether are among the coins that Shuffle's online bitcoin casino names for deposits, alongside its own SHFL token, and the site — which operates under a license from Curacao — ties each credit to blockchain confirmation.

Beyond bitcoin, those coins mostly buy a faster clock. Litecoin Core targets a block every 2.5 minutes. Ethereum runs a slot every 12 seconds, though by ethereum.org's own estimate a block needs about 15 minutes to become final. Solana moved to 300-millisecond slots in late August and finalizes in about 12.8 seconds, and the Solana Foundation says the Alpenglow upgrade, expected in a release targeted for October, aims for finality in roughly 150 milliseconds — a figure to check against the live chain once the release actually ships.

Dollar tokens — stablecoins built to track the US dollar — go after the price problem. USDT was quoted at $0.9996 on Coinbase the same day, so a transfer in flight barely drifts — but the token pays its chain's fee in that chain's own coin, because a token rides on top of a chain's native currency rather than being one itself. Solana's documentation says every transaction there “requires a fee paid in SOL.” In Ethereum block 26,082,776, 60 plain USDT transfers used 41,297 to 63,221 gas, about two to three times the 21,000 that ethereum.org gives for a basic ETH transfer, and cost roughly 9 to 49 cents each in ETH at $2,716.88 — 20 cents at the median. A wallet holding USDT and no ETH cannot make an ordinary transfer.

The network matters as much as the coin. Tether lists more than a dozen supported networks, from Ethereum and Tron to Solana, TON and Aptos, and has stopped issuing on five older chains, among them the Omni Layer that once carried USDT on bitcoin. Whichever network sits beside a USDT line sets the clock and the fee coin.

Side by side, from each project's own documentation and the chain data above:

A Withdrawal Retraces the Deposit, Then Becomes Final

Getting money out runs back along the route it came in on. Under Shuffle's terms of service, a withdrawal is paid in the same currency as the deposit it can be traced to, so bitcoin sent in returns as bitcoin, and the operator may ask for proof that the receiving wallet is held in the player's name.

Identity checks ride along. The same terms reserve the operator's right to request documents whenever it sees fit and to require a government ID before money first leaves the account. When the Consumer Financial Protection Bureau reviewed crypto complaints in 2022, identity verification problems were among the reasons people gave for being unable to reach their funds. No coin changes may hold an account, either: people located or resident in the United States are among those the terms turn away.

Speed on the way out starts as the operator's call. The terms promise no particular processing time and allow a network fee to come off the amount, and once a withdrawal is broadcast the network's clock takes over again.

Then the transfer is final. The Federal Trade Commission's consumer guidance on cryptocurrency says crypto payments “typically are not reversible” and that money usually comes back only “if the person you paid sends it back.” The terms carry that into withdrawals: coins sent to a wrong address, or over a network the receiving wallet does not support, may never be recovered, and the operator has no duty to try.

The 14-cent payment in block 969,146 was checkable at every step, yet nothing in that public record could have pulled it back had its destination been wrong. Whether coins are headed to a cashier or coming back from one, catching a wrong address or a mismatched network falls to the person pressing send.

Source: FinTechZoom