← previous blocknext block →recent activity

Analyzing

Block #89,666,220

23 transactions · 22 stateful · 2026-07-23 15:23:08 UTC

Parallelism

78/100

Blocked

32%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,666,220  ·  23 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

0xf1cc9519…84c1

0x34b655…2a6f

8 touches
6 conflicts

0x366748e9…1282

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x861e5aef…d32c

0x34b655…2a6f

6 touches
3 conflicts

0x63fc5b04…82ae

0x34b655…2a6f

6 touches
3 conflicts

0x1fd98771…f62e

0x34b655…2a6f

4 touches
1 conflict

0x351fa26b…2018

0x34b655…2a6f

4 touches
1 conflict

0x3e505a15…70f8

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

6 conflicts on slot 0xf1cc9519e3…fe84c1

← previous block·next block →recent activity