← previous blocknext block →recent activity

Analyzing

Block #91,162,238

20 transactions · 19 stateful · 2026-07-28 21:14:07 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,162,238  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x4943c7e5…d013

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x2bde601f…00eb

0x34b655…2a6f

6 touches
3 conflicts

0xa8dad04b…f666

0x34b655…2a6f

6 touches
3 conflicts

0xab354035…b07c

0x34b655…2a6f

6 touches
3 conflicts

0x803cd43b…b348

0x34b655…2a6f

4 touches
1 conflict

0x81561f70…fefd

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: Perpl

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity