← previous blocknext block →recent activity

Analyzing

Block #80,484,085

25 transactions · 21 stateful · 2026-06-11 01:55:30 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #80,484,085  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x353d39c0…41da

0xd32edf…ff58

9 touches
10 conflicts

0x5e24c5e6…330d

0x754704…b603

6 touches
3 conflicts

0x90f07a4f…d932

0x34b655…2a6f

4 touches
1 conflict

0x57bb625a…286d

0x34b655…2a6f

4 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 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

10 conflicts on slot 0x353d39c056…3641da

← previous block·next block →recent activity