← previous blocknext block →recent activity

Analyzing

Block #86,660,248

23 transactions · 21 stateful · 2026-07-09 16:37:30 UTC

Parallelism

61/100

Blocked

48%

Avg conflicts / tx

1.09

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,660,248  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0x3a2a8323…3f40

0x34b655…2a6f

8 touches
6 conflicts

0x5b813b1d…5968

0x34b655…2a6f

8 touches
6 conflicts

0x1782a68f…8429

0x34b655…2a6f

8 touches
6 conflicts

0x9021aa0c…20ac

0x34b655…2a6f

8 touches
6 conflicts

0xd786a4f1…12d6

0x34b655…2a6f

8 touches
6 conflicts

0xdfe311f9…a651

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

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

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity