← previous blocknext block →recent activity

Analyzing

Block #86,247,874

27 transactions · 23 stateful · 2026-07-07 18:39:26 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.93

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,247,874  ·  27 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xacc3059c…83af

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xa87de99c…8c74

0x34b655…2a6f

4 touches
1 conflict

0xcc25f1e5…2cac

0x34b655…2a6f

4 touches
1 conflict

0xe732567d…b65d

0x34b655…2a6f

4 touches
1 conflict

0xea201b09…995b

0x34b655…2a6f

4 touches
1 conflict

0xf0217b2d…5aa3

0x34b655…2a6f

4 touches
1 conflict

0xffb8950c…23c6

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

15 conflicts on slot 0xacc3059c89…ba83af

← previous block·next block →recent activity