← previous blocknext block →recent activity

Analyzing

Block #87,922,342

40 transactions · 20 stateful · 2026-07-15 13:16:32 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,922,342  ·  40 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

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xc788862c…c259

0x34b655…2a6f

6 touches
3 conflicts

0x4360b49f…140d

0x34b655…2a6f

6 touches
3 conflicts

0x36f9663c…6c66

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x4ce41dcc…e297

0x34b655…2a6f

4 touches
1 conflict

0x552908a1…e44f

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 0x0733be30d6…38112f

← previous block·next block →recent activity