← previous blocknext block →recent activity

Analyzing

Block #86,709,272

28 transactions · 21 stateful · 2026-07-09 22:04:36 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,709,272  ·  28 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

16 touches
28 conflicts

0xd786a4f1…12d6

0x34b655…2a6f

8 touches
6 conflicts

0xdfe311f9…a651

0x34b655…2a6f

8 touches
6 conflicts

0xed660153…a905

0x34b655…2a6f

8 touches
6 conflicts

0x548145a9…cfce

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x63b15849…80b2

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 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

28 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity