← previous blocknext block →recent activity

Analyzing

Block #87,730,231

19 transactions · 16 stateful · 2026-07-14 15:51:31 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

1.16

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,730,231  ·  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

0x5ec64628…72e4

0x34b655…2a6f

10 touches
10 conflicts

0x2d7ea048…d78e

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x1941b441…5889

0x34b655…2a6f

6 touches
3 conflicts

0x344bc09a…942f

0x34b655…2a6f

6 touches
3 conflicts

0x366c7d57…0ed1

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x680ca7d7…2df4

0x34b655…2a6f

6 touches
3 conflicts

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 0x5ec6462858…6272e4

← previous block·next block →recent activity