← previous blocknext block →recent activity

Analyzing

Block #86,332,135

28 transactions · 24 stateful · 2026-07-08 04:02:02 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,332,135  ·  28 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

0x90f05eed…757d

0xd32edf…ff58

9 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x6925adc4…13c7

0x065c9d…c394

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x4b1c2ed5…53a2

0x40c49f…2af0

3 touches
1 conflict

0x0b55ddd4…77e2

0x188d58…ea8e

2 touches
0 conflicts

0x0b55ddd4…77e3

0x188d58…ea8e

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 0x90f05eed73…55757d

← previous block·next block →recent activity