← previous blocknext block →recent activity

Analyzing

Block #82,564,436

23 transactions · 19 stateful · 2026-06-20 17:05:12 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.09

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #82,564,436  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x64635d33…f40c

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x8b305a3b…1c34

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd3a433e6…2fad

0x34b655…2a6f

6 touches
3 conflicts

0x8b305a3b…1c35

0x34b655…2a6f

6 touches
3 conflicts

0x0bfd53c0…dee0

0x34b655…2a6f

5 touches
3 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: FastLane: FastLaneAuctionHandler

15 conflicts on slot 0x64635d3313…bdf40c

← previous block·next block →recent activity