← previous blocknext block →recent activity

Analyzing

Block #87,310,329

23 transactions · 20 stateful · 2026-07-12 17:02:27 UTC

Parallelism

65/100

Blocked

55%

Avg conflicts / tx

1.57

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,310,329  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xfaef08b1…0696

0x34b655…2a6f

14 touches
21 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x3ef0952c…762d

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4ab

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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity