← previous blocknext block →recent activity

Analyzing

Block #89,539,809

20 transactions · 19 stateful · 2026-07-23 01:34:03 UTC

Parallelism

75/100

Blocked

32%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,539,809  ·  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

0xa08f40b2…9a93

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2bac71c3…3296

0x34b655…2a6f

4 touches
1 conflict

0x2c283b20…35da

0x34b655…2a6f

4 touches
1 conflict

0x2debe664…1818

0x34b655…2a6f

4 touches
1 conflict

0x6bd6b33e…9557

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 0xa08f40b255…099a93

← previous block·next block →recent activity