← previous blocknext block →recent activity

Analyzing

Block #86,444,375

28 transactions · 23 stateful · 2026-07-08 16:31:48 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.43

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,444,375  ·  28 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

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x157dbfb2…4089

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x7506443a…4820

0x34b655…2a6f

6 touches
3 conflicts

0xb1c67a7d…b9b1

0x34b655…2a6f

6 touches
3 conflicts

0xb46ee126…a1a5

0x34b655…2a6f

6 touches
3 conflicts

0xd3ef5630…0de9

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