← previous blocknext block →recent activity

Analyzing

Block #87,663,398

22 transactions · 19 stateful · 2026-07-14 08:24:16 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.91

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,663,398  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x571cb36d…3b3d

0x34b655…2a6f

8 touches
6 conflicts

0x741cc881…a8da

0x34b655…2a6f

8 touches
6 conflicts

0xf324b405…ca30

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x8d3b947a…7da6

0x34b655…2a6f

6 touches
3 conflicts

0xc8fec9ca…2d60

0x34b655…2a6f

6 touches
3 conflicts

0xcffc8fcf…ff81

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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 0x571cb36db3…a33b3d

← previous block·next block →recent activity