Read the whole blockchain receipt—not only the transaction ID

An Ethereum-style blockchain receipt is not the same as a casino cashier receipt. The blockchain record describes a signed state-changing instruction and its execution, while the casino ledger decides which account receives credit. Reading both records together is the only reliable way to explain a deposit or withdrawal.

Ethereum.org identifies core transaction fields including sender, recipient, signature, nonce, value, input data and gas settings. It also explains the lifecycle from hash generation and broadcast to block inclusion and finalization. These facts describe Ethereum transactions generally; they do not confirm any casino’s New Zealand availability or payment policy.

Start with the correct network

Open the explorer for the exact chain used by the cashier. An Ethereum-looking address can appear on several EVM-compatible networks, but a transaction hash exists only on the chain where it was broadcast. The wrong explorer may show no result or an unrelated record.

Record the network name, chain identifier where available, explorer URL and transaction hash. Do not assume that “ERC-20” alone identifies the full route; confirm the operator’s current network instruction.

If the casino cites a Layer 2 or sidechain, use that network’s explorer and finality model. The general Ethereum source cannot establish operator support for it.

Hash and status

The transaction hash is generated from the signed transaction and identifies the broadcast instruction. Copy it exactly from the wallet, exchange or casino record.

An explorer can show pending, included, successful or failed states. Inclusion in a block is not the same as finalization, and successful execution is not the same as casino credit. Save the block number and timestamp alongside status.

If no hash exists, the request may still be internal to a wallet, exchange or casino. Do not call it an on-chain transaction until the network can locate it.

Sender and recipient fields

The from address identifies the signer or transaction origin. The to field can be an externally owned account or a smart contract. Compare the to address with the fresh casino deposit instruction or the withdrawal destination.

For contract-mediated token transfers, the top-level to may be the token contract rather than the final recipient. The actual beneficiary can appear in decoded input or event logs. Do not conclude that funds went to the contract owner merely from the top-level field.

Save complete addresses. First-and-last-character checks are useful during manual comparison but not sufficient for evidence.

Native value versus token amount

Ethereum’s value field is denominated in wei and represents native ETH sent by the transaction. One ETH equals 10^18 wei. A token transfer can have zero native value while moving tokens through contract data and logs.

For an ETH deposit, convert the value using the correct decimal unit and compare it with the cashier request. For an ERC-20 token, inspect the decoded transfer event, token contract, recipient and raw amount using that token’s declared decimals.

Do not report the gas fee as part of the recipient amount. The sender pays gas separately from the transferred value.

Token contract identity

Tickers are not unique. Confirm the token contract address against the casino’s supported asset instruction. A transaction can transfer a token labelled USDT or USDC from an unsupported contract even when the ticker looks correct.

Record contract address, token name, symbol, decimals and network. Treat explorer labels as convenience metadata and verify them against primary operator documentation.

If the receipt shows an unfamiliar proxy or bridge contract, do not guess the credited asset. Ask the operator whether that route is supported.

Input data and function calls

Transactions that interact with contracts carry input data. The first four bytes commonly identify the called function, while the remaining data encode arguments. An explorer may decode the call as transfer, transferFrom, a swap, bridge or another method.

Read the decoded intent before treating the record as a simple payment. A swap may deliver a different token, and a bridge may settle on another network. A token approval authorizes spending but does not itself send the casino a deposit.

Where the explorer cannot decode the call, retain the raw data and contract address. Do not rely on blind interpretation of hexadecimal bytes.

Event logs as token receipts

ERC-20 transfers are commonly represented by contract event logs. Find the event matching the supported token contract, intended casino address and expected amount.

A transaction can contain several transfer events. Identify which one represents the final payment rather than summing every internal movement. Swaps and routers can emit incoming and outgoing events for several assets.

Record log index, token contract, sender, recipient and normalized amount. This becomes the token-specific receipt linked to the parent transaction hash.

Batch payouts

A casino or payment processor can send multiple withdrawals in one transaction or through a contract that emits multiple transfer events. The top-level transaction amount may therefore represent a batch rather than one player’s payout.

Locate the output or event addressed to the user’s destination. Use that amount, not the total value moved by the transaction. Pair it with the casino withdrawal request ID.

Privacy matters: do not publish other recipients from the batch. Redact unrelated transfers when sharing screenshots.

Nonce and replacement context

The nonce is a sequential counter for transactions from an externally owned account. Two pending transactions from the same sender using the same nonce can indicate replacement, but interpreting sender-side replacement requires control and full context.

A casino user should not assume a payment vanished because one hash was replaced. Ask the sender for the final hash and compare nonce, destination and value on the network.

The nonce does not identify the casino account or payment request. Keep it as technical context, not a customer reference.

Gas fields and actual fee

Ethereum transactions specify gas limit and fee parameters such as maximum fee and priority fee. The actual fee depends on gas used and the included block’s fee conditions.

Record gas used, effective gas price and total fee from the receipt. Do not subtract the fee from the recipient’s token amount unless the wallet or operator explicitly structured the payment that way.

A high fee does not make the transfer amount larger or improve casino credit. It pays for network execution.

Successful versus failed execution

A failed contract transaction can be included in a block and consume gas without completing the intended token transfer. Check receipt status and event logs.

If status is failed, do not report the requested input amount as delivered. The sender may still have paid gas. Use the wallet and operator support process before attempting another transfer.

If status is successful but no expected transfer event exists, inspect the called function. Success means the contract execution did not revert; it does not guarantee the user’s intended business outcome.

Pending, included, justified and finalized

Ethereum.org describes broadcast into a transaction pool, validator inclusion and later consensus stages such as justified and finalized. Record which stage the explorer exposes.

The casino can choose its own confirmation or finality threshold. The general protocol documentation does not define a universal deposit-credit time. Keep network state and casino credit state separate.

Do not send a duplicate solely because a transaction is pending. First determine whether it is still in the pool, replaced, dropped or included under another hash.

Reading an ETH deposit receipt

For a simple ETH transfer, compare network, sender, to, native value, status, block, timestamp and fee. Then compare the casino’s generated address and credited ledger amount.

The account debit can equal transfer value plus gas, while the recipient receives the transfer value. An NZD estimate can change with price and should not replace the native-unit record.

If the casino credits a converted balance, record its quoted rate and time as a separate operator-side calculation.

Reading an ERC-20 deposit receipt

For a token payment, verify the top-level transaction status, token contract and relevant Transfer event. Normalize the raw amount using the token’s decimals and compare the event recipient with the casino instruction.

The native ETH value can be zero, while gas is still paid in the network’s native asset. Do not call zero value a zero-value token transfer.

If a memo or account identifier is encoded in contract data, ask the operator how it is mapped. Standard Ethereum transfers do not have one universal casino memo convention.

Reading a casino withdrawal

Start with the operator’s withdrawal request ID, asset, network, destination and approved amount. Locate the transaction hash and then the exact output or token event paying the user’s address.

For a batched transaction, ignore other recipients. Compare the credited wallet amount with the relevant event and document any fee disclosed by the operator.

If the casino marks complete but no hash resolves, request clarification. An internal processor reference is not proof of broadcast.

Evidence table

Create one row for the casino request, one for the blockchain transaction and one for the wallet or account credit. Fields should include identifiers, asset, network, address, native amount, token amount, fee, status and timestamps.

Mark the source of each field. The explorer proves public network state; the casino ledger proves account mapping; the wallet proves local receipt. None replaces the others.

Keep screenshots redacted and preserve original hashes as text to prevent transcription errors.

Common interpretation errors

Do not treat top-level ETH value as an ERC-20 amount. Do not call an approval a transfer. Do not use total batch value as one withdrawal. Do not confuse gas limit with actual fee.

A successful transaction can still send the wrong token or address. A finalized transaction can still remain uncredited by the casino. Conversely, a pending operator request may not yet have any network record.

The receipt shows what the chain executed, not whether the casino is licensed, trustworthy or available in New Zealand.

Dispute checklist

Provide authenticated support with request ID, transaction hash, network, sender, recipient, token contract, relevant log index, amount, block and timestamp. Explain the mismatch precisely.

Never share a private key, seed phrase or one-time code. Public transaction data are enough to locate the transfer.

If a third party offers recovery in exchange for another crypto payment, stop. A receipt can be analysed without granting wallet access.

New Zealand and source scope

Ethereum.org documents protocol mechanics, not casino access, operator limits, processing promises or New Zealand law. Verify those through current primary operator and official local sources.

Keep a crypto amount and an NZD budget side by side. Price volatility can make fiat displays differ even when the on-chain amount is correct.

Final receipt audit

Confirm network, hash, status, sender, destination, native value, token event, gas, block and finality. Then match the casino request and ledger credit.

If all three layers agree, the receipt is complete. If they diverge, identify the first mismatching field rather than labelling the entire transfer “missing.”

A transaction ID is a locator, not a complete receipt. Ethereum transactions are signed instructions that change network state. A hash identifies the submitted transaction, but the user still needs to verify which network processed it, who sent it, what address received it, whether native ETH or a contract was involved, and whether the block reached the required status.

The Ethereum source explains transaction fields and lifecycle. It does not establish any casino’s New Zealand availability, internal withdrawal ID, batching policy, token-crediting rules or support timeline. Those details must come from the operator’s authenticated cashier.

Start with network and hash

Open the hash in an explorer for the exact network named by the cashier. The same-looking address can exist on more than one EVM-compatible chain, so an explorer result on the wrong network is not evidence for the requested withdrawal.

Ethereum.org explains that a transaction hash is generated after submission, then the transaction enters the network pool. A validator must include it in a block before it can be treated as successful; the block later progresses through stronger states toward finalization.

Record the full hash, network, block number, timestamp and status. Do not rely on a cropped screenshot or a link supplied by an unknown support account.

Read the core fields

Ethereum transactions include from, to, value, nonce, optional input data, gas limit and fee fields. The sender signs the transaction; the signature proves authorisation by the corresponding private key.

• from identifies the signing account.
• to can be a recipient account or a smart contract.
• value is native ETH measured in wei, where 1 ETH equals 10^18 wei.
• input data can instruct a contract to perform another action.
• the nonce orders transactions from the sending account.
• gas and fee fields describe execution cost, not the amount credited to the player.

A zero native value does not automatically mean no token moved: it can be a contract interaction. Conversely, a successful contract call does not prove that a casino assigned the transfer to the correct account.

Token transfers and contract data

Ethereum.org shows that contract calls can encode a function and arguments in the input field. Its example identifies the common transfer(address,uint256) selector and decodes a recipient and amount. This illustrates why an explorer’s human-readable summary must be checked against the underlying contract and calldata.

The supplied source does not document a universal “token transfer” receipt layout or a casino-specific token log. Explorer labels are conveniences, not the signed instruction itself. Check the token contract, decimals, recipient and quantity; do not identify a token only by its ticker or icon.

Batch payouts

A casino may associate several customer withdrawals with one contract execution, but the Ethereum transaction guide does not define casino batching. If the to field points to a payout contract rather than the customer wallet, the main value line alone may not identify the individual allocation.

Ask support for the withdrawal ID, transaction hash, asset contract, destination and the exact amount attributed to the account. One transaction’s fee is also not necessarily a per-customer charge when several transfers are processed together.

Status and finality

Ethereum.org describes a lifecycle from broadcast to inclusion, then justified and finalized blocks. “Successful” indicates execution at network level; it does not confirm that an exchange or casino has completed its own account posting. A failed transaction can still consume gas.

Keep the cashier status alongside the chain status. If they disagree, provide authenticated support with the withdrawal ID and full hash, not a private key or seed phrase.

Evidence checklist

Save the network, hash, from, to, native value, input type, token contract where relevant, destination, amount, block, timestamp, status and withdrawal ID. For a batch, ask which decoded transfer belongs to the account. Never publish unrelated recipient addresses from the same transaction.

Frequently asked questions

Is the transaction hash enough to prove a payout? No. Match its network, destination, asset, amount and cashier withdrawal ID.

Why can native value show zero? The transaction may call a contract rather than transfer ETH directly.

Is gas the amount received? No. Gas is the execution fee.

Does “successful” mean the casino account is credited? No. It confirms network execution, not the operator’s internal posting.

Can one transaction contain several customer payouts? A contract can perform complex actions, but the supplied source does not confirm any casino batching policy.

Is New Zealand casino availability confirmed? No.

Official source

• Ethereum.org: Transactions

Bottom line: use the hash to open the receipt, then reconcile every relevant field with the cashier record and the intended wallet.