← previous blocknext block →recent activity

Analyzing

Block #82,807,146

43 transactions · 34 stateful · 2026-06-21 20:08:14 UTC

Parallelism

81/100

Blocked

59%

Avg conflicts / tx

1.56

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #82,807,146  ·  43 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

0xaa42ca7f…6551

0xd32edf…ff58

15 touches
28 conflicts

0x217bd767…b79e

0x34b655…2a6f

14 touches
21 conflicts

0xf3d10975…0d07

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xc0f29314…17fa

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 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

28 conflicts on slot 0xaa42ca7f39…6e6551

← previous block·next block →recent activity