← previous blocknext block →recent activity

Analyzing

Block #87,615,989

23 transactions · 21 stateful · 2026-07-14 03:07:25 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,615,989  ·  23 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

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x5bd818fc…4f86

0x34b655…2a6f

4 touches
1 conflict

0x60e95cf4…3f88

0x34b655…2a6f

4 touches
1 conflict

0x6ac6d1bf…8b19

0x34b655…2a6f

4 touches
1 conflict

0x73ca2093…8dd6

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09c

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09d

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 0x92385428ad…dc6941

← previous block·next block →recent activity