← previous blocknext block →recent activity

Analyzing

Block #87,332,397

20 transactions · 17 stateful · 2026-07-12 19:30:03 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

1.05

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,332,397  ·  20 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

0x64aaadbf…f9f3

0x34b655…2a6f

10 touches
10 conflicts

0xc1a85015…c5c4

0xd32edf…ff58

9 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x7048d42f…288b

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

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 0x64aaadbf0a…79f9f3

← previous block·next block →recent activity