← previous blocknext block →recent activity

Analyzing

Block #89,515,675

20 transactions · 19 stateful · 2026-07-22 22:52:55 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

1.1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,515,675  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xb96d82ef…f5ee

0x34b655…2a6f

8 touches
6 conflicts

0xf1cc9519…84c1

0x34b655…2a6f

6 touches
3 conflicts

0x1e120cc8…7049

0x34b655…2a6f

6 touches
3 conflicts

0x8ad18e06…472a

0x34b655…2a6f

6 touches
3 conflicts

0x91b0f8ed…6bd6

0x34b655…2a6f

4 touches
1 conflict

0x91b0f8ed…6bd7

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity