← previous blocknext block →recent activity

Analyzing

Block #91,269,047

17 transactions · 17 stateful · 2026-07-29 06:11:46 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.35

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,269,047  ·  17 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

0x9e346341…6e3f

0xd32edf…ff58

11 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x5af098c7…4806

0x34b655…2a6f

6 touches
3 conflicts

0x216ffe66…1f94

0x34b655…2a6f

6 touches
3 conflicts

0x5af098c7…4807

0x34b655…2a6f

6 touches
3 conflicts

0x65c5c2dc…cdde

0x34b655…2a6f

6 touches
3 conflicts

0x91b0f8ed…6bd6

0x34b655…2a6f

6 touches
3 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

15 conflicts on slot 0x9e34634114…266e3f

← previous block·next block →recent activity