← previous blocknext block →recent activity

Analyzing

Block #87,709,563

22 transactions · 21 stateful · 2026-07-14 13:33:06 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,709,563  ·  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

0x0dd44476…ef40

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x1f5dc61b…2471

0x34b655…2a6f

6 touches
3 conflicts

0x6f46250b…3bf2

0x34b655…2a6f

6 touches
3 conflicts

0x6e088aaa…3972

0x34b655…2a6f

4 touches
1 conflict

0x70d66bd9…0ffa

0x34b655…2a6f

4 touches
1 conflict

0x775a8ad3…8307

0x34b655…2a6f

4 touches
1 conflict

0x7a4f47ac…3289

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

10 conflicts on slot 0x0dd44476b8…7fef40

← previous block·next block →recent activity