← previous blocknext block →recent activity

Analyzing

Block #87,688,852

22 transactions · 21 stateful · 2026-07-14 11:14:22 UTC

Parallelism

77/100

Blocked

43%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,688,852  ·  22 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

0xb8431b57…6825

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x16db7423…9892

0x34b655…2a6f

4 touches
1 conflict

0x369883e3…a449

0x34b655…2a6f

4 touches
1 conflict

0x4bbf32ef…15b8

0x34b655…2a6f

4 touches
1 conflict

0x4bbf32ef…15b9

0x34b655…2a6f

4 touches
1 conflict

0x53f393fa…00b9

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

3 conflicts on slot 0xb8431b57db…e96825

← previous block·next block →recent activity