← previous blocknext block →recent activity

Analyzing

Block #86,056,111

26 transactions · 17 stateful · 2026-07-06 21:19:22 UTC

Parallelism

85/100

Blocked

41%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,056,111  ·  26 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

0x6377f3f7…381a

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x95523e2a…4c01

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xda2ee2e7…968a

0x34b655…2a6f

4 touches
1 conflict

0xfd42a6b9…4c81

0x34b655…2a6f

4 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

2 touches
0 conflicts

0x09beabbc…065e

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

6 conflicts on slot 0x6377f3f70a…19381a

← previous block·next block →recent activity