← previous blocknext block →recent activity

Analyzing

Block #89,751,396

26 transactions · 24 stateful · 2026-07-23 22:33:47 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,751,396  ·  26 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x31684331…a008

0x34b655…2a6f

6 touches
3 conflicts

0xfab1627b…b819

0x34b655…2a6f

4 touches
1 conflict

0x286711a5…b3bf

0x34b655…2a6f

4 touches
1 conflict

0xa80684c9…3948

0x34b655…2a6f

4 touches
1 conflict

0xcef70a96…db44

0x34b655…2a6f

4 touches
1 conflict

0xd6d040d9…9ae3

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 0xac2a02739b…81721b

← previous block·next block →recent activity