← previous blocknext block →recent activity

Analyzing

Block #86,958,065

20 transactions · 18 stateful · 2026-07-11 01:47:24 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,958,065  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xeed960a5…a619

0xd32edf…ff58

7 touches
6 conflicts

0x248e43aa…7287

0x34b655…2a6f

4 touches
1 conflict

0x35b89cd8…5092

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x816c7d6d…98ea

0x34b655…2a6f

4 touches
1 conflict

0x816c7d6d…98eb

0x34b655…2a6f

4 touches
1 conflict

0x94e7f277…471b

0x34b655…2a6f

4 touches
1 conflict

0xee4fe1f7…3ead

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

6 conflicts on slot 0xeed960a5f3…2da619

← previous block·next block →recent activity