← previous blocknext block →recent activity

Analyzing

Block #87,663,438

21 transactions · 17 stateful · 2026-07-14 08:24:32 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,663,438  ·  21 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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xc8304415…4f91

0x34b655…2a6f

6 touches
3 conflicts

0x80398c66…f3cc

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x326f2a00…a2a6

0x34b655…2a6f

6 touches
3 conflicts

0x52bca89b…97d8

0x34b655…2a6f

4 touches
1 conflict

0x592489d4…e988

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity