← previous blocknext block →recent activity

Analyzing

Block #87,682,735

21 transactions · 20 stateful · 2026-07-14 10:33:28 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,682,735  ·  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

0x08330b36…ae29

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0x34d95d94…3a16

0x34b655…2a6f

6 touches
3 conflicts

0x91d48be7…e4e8

0x34b655…2a6f

6 touches
3 conflicts

0xfd04e719…6320

0x34b655…2a6f

6 touches
3 conflicts

0xa10e928f…3b92

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

6 touches
3 conflicts

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 0x08330b3687…a7ae29

← previous block·next block →recent activity