← previous blocknext block →recent activity

Analyzing

Block #86,791,238

27 transactions · 24 stateful · 2026-07-10 07:12:08 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

1.15

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,791,238  ·  27 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

14 touches
21 conflicts

0x3d200f4e…b4bd

0x34b655…2a6f

6 touches
3 conflicts

0x42aad825…b067

0x34b655…2a6f

6 touches
3 conflicts

0x44b0e9be…9ba8

0x34b655…2a6f

6 touches
3 conflicts

0x44fc2746…0a53

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x4cdf55e1…0f2d

0x34b655…2a6f

6 touches
3 conflicts

0x66f7b1ee…a38b

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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity