← previous blocknext block →recent activity

Analyzing

Block #87,595,691

21 transactions · 18 stateful · 2026-07-14 00:51:41 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,595,691  ·  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

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x2dfde2ed…8801

0x34b655…2a6f

6 touches
3 conflicts

0x38bad1f8…ee45

0x34b655…2a6f

6 touches
3 conflicts

0x53bddbe8…2e5e

0x34b655…2a6f

6 touches
3 conflicts

0x5b145de0…367c

0xc8689a…ee79

6 touches
3 conflicts

0x26050074…6967

0x34b655…2a6f

6 touches
3 conflicts

0xd19c9d38…b459

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 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity