← previous blocknext block →recent activity

Analyzing

Block #87,295,604

22 transactions · 22 stateful · 2026-07-12 15:24:03 UTC

Parallelism

82/100

Blocked

27%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,295,604  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7749b313…08bb

0x34b655…2a6f

4 touches
1 conflict

0x7d3c50c5…2279

0x34b655…2a6f

4 touches
1 conflict

0x833d2d11…e7ba

0x34b655…2a6f

4 touches
1 conflict

0x875c3459…2878

0x34b655…2a6f

4 touches
1 conflict

0x875c3459…2879

0x34b655…2a6f

4 touches
1 conflict

0x974c36fe…1cd7

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

6 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity