← previous blocknext block →recent activity

Analyzing

Block #87,920,927

25 transactions · 21 stateful · 2026-07-15 13:07:04 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,920,927  ·  25 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

0x6689d73a…ba50

0x34b655…2a6f

6 touches
3 conflicts

0xc788862c…c259

0x34b655…2a6f

6 touches
3 conflicts

0x405da62e…192a

0xa6afd3…d132

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x70cfbacf…5c46

0x34b655…2a6f

4 touches
1 conflict

0x7cfe59e0…2ec1

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0x6689d73aac…09ba50

← previous block·next block →recent activity