← previous blocknext block →recent activity

Analyzing

Block #86,628,914

17 transactions · 14 stateful · 2026-07-09 13:06:49 UTC

Parallelism

65/100

Blocked

64%

Avg conflicts / tx

1.12

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,628,914  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x1951ee47…540f

0x34b655…2a6f

8 touches
6 conflicts

0x22bc4ea4…5c8a

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

8 touches
6 conflicts

0x6b2ba712…0214

0x34b655…2a6f

8 touches
6 conflicts

0x727fbce7…0c80

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

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity