← previous blocknext block →recent activity

Analyzing

Block #87,262,926

23 transactions · 21 stateful · 2026-07-12 11:45:33 UTC

Parallelism

65/100

Blocked

48%

Avg conflicts / tx

1.7

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,262,926  ·  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

0xbf78ee7f…e7fd

0x34b655…2a6f

14 touches
21 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

14 touches
21 conflicts

0x493b81c1…688d

0x34b655…2a6f

10 touches
10 conflicts

0x5a310d83…cae0

0x34b655…2a6f

10 touches
10 conflicts

0x5f72d58f…c445

0x34b655…2a6f

10 touches
10 conflicts

0x0733be30…112f

0x34b655…2a6f

10 touches
10 conflicts

0xd1ec0dfd…ccc0

0xc8689a…ee79

10 touches
10 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