← previous blocknext block →recent activity

Analyzing

Block #89,377,631

21 transactions · 20 stateful · 2026-07-22 07:30:25 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,377,631  ·  21 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

0x0dd44476…ef40

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x1bb624f3…c1b3

0x34b655…2a6f

4 touches
1 conflict

0x63c5df66…1701

0x34b655…2a6f

4 touches
1 conflict

0x79b67e06…8d60

0x34b655…2a6f

4 touches
1 conflict

0xbfb7adca…51d7

0x34b655…2a6f

4 touches
1 conflict

0xc3baa205…f26e

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 0x0dd44476b8…7fef40

← previous block·next block →recent activity