← previous blocknext block →recent activity

Analyzing

Block #89,560,153

22 transactions · 18 stateful · 2026-07-23 03:49:57 UTC

Parallelism

68/100

Blocked

39%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,560,153  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

4 touches
1 conflict

0x1408a100…f721

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2d024ef0…2a81

0x34b655…2a6f

4 touches
1 conflict

0x2debe664…1818

0x34b655…2a6f

4 touches
1 conflict

0x32409e80…a396

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity