- Is this just a plain QRL2 transfer with no contract involved?
- Yes. A native QRL2 transfer moves the protocol's base asset directly from one externally-owned account to another — the recipient's balance increases by the Amount shown, the sender's balance decreases by Amount + fee. No smart contract is invoked, no input data is attached, no token contract is involved. This is the simplest and cheapest transaction shape on QRL 2.0.
- Why doesn't the recipient appear to receive the fee?
- Only the proposer of the confirming block receives the priority-fee tip. The base-fee portion (the bulk of the cost under EIP-1559) is destroyed by the protocol, not paid to any address. The Transfer diagram above already accounts for both — the fee is shown on the sender's side, on top of the Amount that reaches the recipient.
- 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.