← previous blocknext block →recent activity

Analyzing

Block #91,811,505

20 transactions · 19 stateful · 2026-07-31 03:42:40 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,811,505  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xe00ee51a…f7ab

0xd32edf…ff58

11 touches
15 conflicts

0x217bd767…b79e

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0xc2aacf41…5504

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…00c9

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 0xe00ee51a89…5cf7ab

← previous block·next block →recent activity