← previous blocknext block →recent activity

Analyzing

Block #87,591,926

25 transactions · 22 stateful · 2026-07-14 00:26:29 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,591,926  ·  25 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x4c188934…158e

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x43bc2389…898f

0x34b655…2a6f

4 touches
1 conflict

0x469e824a…d814

0x34b655…2a6f

4 touches
1 conflict

0x4ab0fef9…caef

0x34b655…2a6f

4 touches
1 conflict

0x536588d3…19c5

0x34b655…2a6f

4 touches
1 conflict

0x588c5b6a…60d2

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

3 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity