← previous blocknext block →recent activity

Analyzing

Block #87,610,175

20 transactions · 19 stateful · 2026-07-14 02:28:32 UTC

Parallelism

70/100

Blocked

37%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,610,175  ·  20 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

0x07f69062…03ec

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe9452241…95a3

0x34b655…2a6f

6 touches
3 conflicts

0x1175233a…64e7

0x34b655…2a6f

4 touches
1 conflict

0x1ee4a6d2…6389

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x3f85f288…7c97

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 0x07f6906240…ea03ec

← previous block·next block →recent activity