← previous blocknext block →recent activity

Analyzing

Block #85,221,881

24 transactions · 22 stateful · 2026-07-03 00:40:12 UTC

Parallelism

79/100

Blocked

36%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,221,881  ·  24 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

0x8a5ba115…d620

0xd32edf…ff58

9 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xa678cd56…4fab

0x34b655…2a6f

6 touches
3 conflicts

0xd63e616b…a07d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6f1bd077…2005

0x34b655…2a6f

4 touches
1 conflict

0x7cb2f3fa…4836

0x34b655…2a6f

4 touches
1 conflict

0x7cee1be1…e770

0x34b655…2a6f

4 touches
1 conflict

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 0x8a5ba115c7…5dd620

← previous block·next block →recent activity