← previous blocknext block →recent activity

Analyzing

Block #87,878,357

19 transactions · 17 stateful · 2026-07-15 08:22:19 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,878,357  ·  19 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

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x0dd44476…ef40

0x34b655…2a6f

6 touches
3 conflicts

0x6630d365…74ad

0x34b655…2a6f

6 touches
3 conflicts

0x9d610330…17d2

0x34b655…2a6f

6 touches
3 conflicts

0x50718952…7c75

0x34b655…2a6f

4 touches
1 conflict

0x64a058c6…74a1

0x34b655…2a6f

4 touches
1 conflict

0x7634a3f4…7f24

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4a3

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity