← previous blocknext block →recent activity

Analyzing

Block #87,665,589

17 transactions · 12 stateful · 2026-07-14 08:38:55 UTC

Parallelism

76/100

Blocked

25%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,665,589  ·  17 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

0xd2b87a88…aa57

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x27828c29…9e2f

0x34b655…2a6f

4 touches
1 conflict

0x46a2c3fe…887d

0x34b655…2a6f

4 touches
1 conflict

0x53f393fa…00b9

0x34b655…2a6f

4 touches
1 conflict

0x683dbabb…acd8

0x34b655…2a6f

4 touches
1 conflict

0x7d6e48e8…f2b5

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

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 0xd2b87a882a…65aa57

← previous block·next block →recent activity