← previous blocknext block →recent activity

Analyzing

Block #86,678,716

20 transactions · 17 stateful · 2026-07-09 18:40:43 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,678,716  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

6 touches
3 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0xb2945ca9…9ca5

0x34b655…2a6f

6 touches
3 conflicts

0xb46ee126…a1a5

0x34b655…2a6f

6 touches
3 conflicts

0xba559de1…6d2c

0x34b655…2a6f

6 touches
3 conflicts

0xcaa1fc83…36e9

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

6 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity