← previous blocknext block →recent activity

Analyzing

Block #91,768,832

28 transactions · 25 stateful · 2026-07-31 00:07:59 UTC

Parallelism

71/100

Blocked

52%

Avg conflicts / tx

1.11

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #91,768,832  ·  28 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xed0ca303…2c19

0xd32edf…ff58

13 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x7ec6e62f…94fd

0x34b655…2a6f

6 touches
3 conflicts

0xcb21158b…f18d

0x34b655…2a6f

6 touches
3 conflicts

0x3bd55803…5d4e

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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

21 conflicts on slot 0xed0ca303a2…942c19

← previous block·next block →recent activity