← previous blocknext block →recent activity

Analyzing

Block #89,384,435

21 transactions · 18 stateful · 2026-07-22 08:15:55 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,384,435  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x71ccd3d7…7072

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x63da8263…7a24

0x34b655…2a6f

6 touches
3 conflicts

0x3e6302c8…64f5

0x34b655…2a6f

4 touches
1 conflict

0x53b07ba6…bcd7

0x34b655…2a6f

4 touches
1 conflict

0x5f8b42c6…15aa

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 0x71ccd3d787…f77072

← previous block·next block →recent activity