What did this contract call actually do?

The Action headline shows the function selector (or its decoded human name when Quantascan has the ABI). The contract address called is the To field; whatever it changed under the hood is reflected below — the Transfer diagram (native value, the fee, and any token movements it emitted) and the Decoded token transfers card (if the contract emitted QRC-20/721/1155 Transfer events). The More Details collapsible shows the raw calldata for full byte-level audit.

Why is the Amount usually zero on a contract call?

Most contract calls don't move native QRL2 at the top level — they move token balances inside the contract's own storage, which doesn't count as a native transfer. The token movement is what the Decoded token transfers card surfaces (when present). When you see Amount > 0 on a contract call, it means the sender attached native QRL2 alongside the call (typical for swap-in flows or contract deposits).

Why are token transfers shown separately from the Amount?

The Amount in the cost summary is the native QRL2 value the transaction moved at the top level — typically zero on a token transfer or contract call. Token movements (QRC-20 fungible, QRC-721 NFTs, QRC-1155 multi-tokens — QRL 2.0's smart-contract token standards) happen inside contract storage, not as native chain-level value. The contract signals each movement by emitting a Transfer event in the receipt's logs; the Decoded token transfers card surfaces those events one-by-one with the token contract, sender, recipient, and amount or token ID — so you see exactly which tokens moved alongside the native value.

How can I tell if this transaction is final?

Look at the Finality badge in the action header. It starts as 'head' (just landed, still being attested by the validator committee), advances to 'justified' after one epoch (~2h 8min) and reaches 'finalized' after two epochs (~4h 16min) — at which point the protocol guarantees the transaction can never be reversed (an attacker would need to control more than one-third of total stake and willingly slash it). Most wallets treat 'head' as safe for everyday transfers; exchanges and high-value transfers conventionally wait for finalization.

How was the fee on this transaction calculated?

On QRL 2.0 the fee is gas_used × effective_gas_price, sourced from the transaction's receipt — not the upper-bound max-fee the sender originally signed. The effective gas price is the confirming block's EIP-1559 base fee plus the sender's optional priority tip (capped at the signed maximum). The base fee is destroyed by the protocol; only the priority tip reaches the proposer.

Will the contents of this transaction ever change?

No. Once a transaction is included in a finalized block its hash, sender, recipients, value moved, fee paid, status, and emitted event logs are part of the historical record forever. The URL of this page is also stable: bookmarking or sharing it always returns the same data, even years from now.

Where does this data come from?

Quantascan indexes from a QRL 2.0 archive node we operate ourselves — no third-party API in the pipeline. The transaction body comes from the chain client (qrl_getTransactionByHash — QRL 2.0 uses the qrl_* JSON-RPC namespace, not eth_*), the receipt (status, gas used, effective gas price, contract address, logs) is fetched in parallel, and reorgs are auto-detected so what you see always matches the canonical chain.

QRL—Block—

—

QuantascanAlphaAlphaBlock Explorer & Analytics

QRL 2.0 Testnet Transaction0x850d2b259f76facea8e2f246ef7df031ed925263708e1a9c40ca0e8e7c9d12ac

Name: QRL Transaction 0x850d2b25…
Creator: Quantascan
License: https://creativecommons.org/publicdomain/zero/1.0/

Single transaction on QRL 2.0 Testnet, the Quantum Resistant Ledger's Proof-of-Stake chain. Action, value flow, fee, decoded token transfers and confirming block below.

QRL 2.0 Testnet. These are test coins with no monetary value. This data will be reset when QRL 2.0 launches on mainnet. View live QRL data

QRL 2.0 Testnet Transaction0x850d2b259f76facea8e2f246ef7df031ed925263708e1a9c40ca0e8e7c9d12ac

Single transaction on QRL 2.0 Testnet, the Quantum Resistant Ledger's Proof-of-Stake chain. Action, value flow, fee, decoded token transfers and confirming block below.

QRL 2.0 Testnet. These are test coins with no monetary value. This data will be reset when QRL 2.0 launches on mainnet. View live QRL data

Action

Contract call

Tasselled Hare4x485Q4b76a…9260Furry Wyrmit876Qcd862…a4c2

Confirmed in block #73,224position #05mo ago2026-05-21 20:52:36 UTC236,244 confirmationsFinalized

Transfer

Who sent value to whom in this transaction, fee included.

From

Tasselled Hare4x485Q4b76a…9260

paid 849,305 shor fee

What actually changed

Across all assets

Here's the net effect on each wallet once every part of this transaction (value, fee and token movements) is added up. Each asset is kept separate: Quanta is never mixed with a token.

New to this? Contract calls & internal transfers

SenderTasselled Hare4x485Q4b76a…9260
- received990,000token(base units (token reports no decimals))
- paid0.000849305 Quantain network fees
ContractQ00000…0000

Token & NFT transfers (12)

Decoded from event logs

QRC-1155MintQcd862…a4c2
Lolling Kingfishzu952Q00000…0000Braided Birdwinghy667Q8e61d…e42f
Item: #0 · Quantity: 1
QRC-1155MintQcd862…a4c2
Lolling Kingfishzu952Q00000…0000

Gas

Gas used

339,722/ 339,722

100.0%

Effective gas price

2.5 shor

cap: 2.5 shor maxtip: 2.5 shor priorityEIP-1559

Input data

Checking for a verified contract ABI…

FunctionUnknown selector 0x11b176f7

0x11b176f7

More details: hashes & internals

Transaction hash: 0x850d2b259f76facea8e2f246ef7df031ed925263708e1a9c40ca0e8e7c9d12ac
Block hash: 0x3624ac9f942ab9cbe9464fc23f2901ca877c1b1d834945b0857027bc7fe7184d
Nonce: 12

Event logs (13)

#0Transfer Single (guess)EmitterFurry Wyrmit876Qcd862…a4c2
TransferSingle(address operator, address from, address to, uint256 id, uint256 value)
operatoraddressTasselled Hare4x485Q4b76a…9260
fromaddressLolling Kingfishzu952Q00000…0000
toaddressBraided Birdwinghy667Q8e61d…e42f
iduint2560
value

FAQ about this transaction

Common questions about this page

What did this contract call actually do?: The Action headline shows the function selector (or its decoded human name when Quantascan has the ABI). The contract address called is the To field; whatever it changed under the hood is reflected below — the Transfer diagram (native value, the fee, and any token movements it emitted) and the Decoded token transfers card (if the contract emitted QRC-20/721/1155 Transfer events). The More Details collapsible shows the raw calldata for full byte-level audit.
Why is the Amount usually zero on a contract call?: Most contract calls don't move native QRL2 at the top level — they move token balances inside the contract's own storage, which doesn't count as a native transfer. The token movement is what the Decoded token transfers card surfaces (when present). When you see Amount > 0 on a contract call, it means the sender attached native QRL2 alongside the call (typical for swap-in flows or contract deposits).
Why are token transfers shown separately from the Amount?: The Amount in the cost summary is the native QRL2 value the transaction moved at the top level — typically zero on a token transfer or contract call. Token movements (QRC-20 fungible, QRC-721 NFTs, QRC-1155 multi-tokens — QRL 2.0's smart-contract token standards) happen inside contract storage, not as native chain-level value. The contract signals each movement by emitting a Transfer event in the receipt's logs; the Decoded token transfers card surfaces those events one-by-one with the token contract, sender, recipient, and amount or token ID — so you see exactly which tokens moved alongside the native value.
How can I tell if this transaction is final?: Look at the Finality badge in the action header. It starts as 'head' (just landed, still being attested by the validator committee), advances to 'justified' after one epoch (~2h 8min) and reaches 'finalized' after two epochs (~4h 16min) — at which point the protocol guarantees the transaction can never be reversed (an attacker would need to control more than one-third of total stake and willingly slash it). Most wallets treat 'head' as safe for everyday transfers; exchanges and high-value transfers conventionally wait for finalization.

Action

Contract call

Tasselled Hare4x485Q4b76a…9260Furry Wyrmit876Qcd862…a4c2

Confirmed in block #73,224position #05mo ago2026-05-21 20:52:36 UTC236,244 confirmationsFinalized

Transfer

Who sent value to whom in this transaction, fee included.

From

Tasselled Hare4x485Q4b76a…9260

paid 849,305 shor fee

What actually changed

Across all assets

Here's the net effect on each wallet once every part of this transaction (value, fee and token movements) is added up. Each asset is kept separate: Quanta is never mixed with a token.

New to this? Contract calls & internal transfers

SenderTasselled Hare4x485Q4b76a…9260
- received990,000token(base units (token reports no decimals))
- paid0.000849305 Quantain network fees
ContractQ00000…0000

Token & NFT transfers (12)

Decoded from event logs

QRC-1155MintQcd862…a4c2
Lolling Kingfishzu952Q00000…0000Braided Birdwinghy667Q8e61d…e42f
Item: #0 · Quantity: 1
QRC-1155MintQcd862…a4c2
Lolling Kingfishzu952Q00000…0000

Gas

Gas used

339,722/ 339,722

100.0%

Effective gas price

2.5 shor

cap: 2.5 shor maxtip: 2.5 shor priorityEIP-1559

Input data

Not decoded

This contract's source code is not verified on Quantascan. Any name below is a guess from a list of common function signatures.

FunctionUnknown selector 0x11b176f7

0x11b176f7

Input data

Checking for a verified contract ABI…

FunctionUnknown selector 0x11b176f7

0x11b176f7

More details: hashes & internals

Transaction hash: 0x850d2b259f76facea8e2f246ef7df031ed925263708e1a9c40ca0e8e7c9d12ac
Block hash: 0x3624ac9f942ab9cbe9464fc23f2901ca877c1b1d834945b0857027bc7fe7184d
Nonce: 12

Event logs (13)

#0Transfer Single (guess)
Guessed
EmitterFurry Wyrmit876Qcd862…a4c2
TransferSingle(address operator, address from, address to, uint256 id, uint256 value)
operatoraddressTasselled Hare4x485Q4b76a…9260
fromaddressLolling Kingfishzu952Q00000…0000
toaddressBraided Birdwinghy667Q8e61d…e42f
iduint256

Event logs (13)

#0Transfer Single (guess)EmitterFurry Wyrmit876Qcd862…a4c2
TransferSingle(address operator, address from, address to, uint256 id, uint256 value)
operatoraddressTasselled Hare4x485Q4b76a…9260
fromaddressLolling Kingfishzu952Q00000…0000
toaddressBraided Birdwinghy667Q8e61d…e42f
iduint2560
value

FAQ about this transaction

Common questions about this page

What did this contract call actually do?: The Action headline shows the function selector (or its decoded human name when Quantascan has the ABI). The contract address called is the To field; whatever it changed under the hood is reflected below — the Transfer diagram (native value, the fee, and any token movements it emitted) and the Decoded token transfers card (if the contract emitted QRC-20/721/1155 Transfer events). The More Details collapsible shows the raw calldata for full byte-level audit.
Why is the Amount usually zero on a contract call?: Most contract calls don't move native QRL2 at the top level — they move token balances inside the contract's own storage, which doesn't count as a native transfer. The token movement is what the Decoded token transfers card surfaces (when present). When you see Amount > 0 on a contract call, it means the sender attached native QRL2 alongside the call (typical for swap-in flows or contract deposits).
Why are token transfers shown separately from the Amount?: The Amount in the cost summary is the native QRL2 value the transaction moved at the top level — typically zero on a token transfer or contract call. Token movements (QRC-20 fungible, QRC-721 NFTs, QRC-1155 multi-tokens — QRL 2.0's smart-contract token standards) happen inside contract storage, not as native chain-level value. The contract signals each movement by emitting a Transfer event in the receipt's logs; the Decoded token transfers card surfaces those events one-by-one with the token contract, sender, recipient, and amount or token ID — so you see exactly which tokens moved alongside the native value.
How can I tell if this transaction is final?: Look at the Finality badge in the action header. It starts as 'head' (just landed, still being attested by the validator committee), advances to 'justified' after one epoch (~2h 8min) and reaches 'finalized' after two epochs (~4h 16min) — at which point the protocol guarantees the transaction can never be reversed (an attacker would need to control more than one-third of total stake and willingly slash it). Most wallets treat 'head' as safe for everyday transfers; exchanges and high-value transfers conventionally wait for finalization.