← previous blocknext block →recent activity

Analyzing

Block #87,057,905

23 transactions · 22 stateful · 2026-07-11 12:54:34 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

1.26

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,057,905  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x7e5ea60a…c4aa

0x34b655…2a6f

14 touches
21 conflicts

0x0733be30…112f

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf9c7befd…e532

0x34b655…2a6f

6 touches
3 conflicts

0x8dfef5ae…9361

0x34b655…2a6f

6 touches
3 conflicts

0x671886b7…46fe

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity