← previous blocknext block →recent activity

Analyzing

Block #86,853,345

35 transactions · 29 stateful · 2026-07-10 14:07:23 UTC

Parallelism

69/100

Blocked

48%

Avg conflicts / tx

1.29

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #86,853,345  ·  35 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x4e3abeff…18eb

0x34b655…2a6f

10 touches
10 conflicts

0x5d863b2f…bd28

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xc788862c…c259

0x34b655…2a6f

8 touches
6 conflicts

0x1d6d6ad8…a4a7

0x34b655…2a6f

6 touches
3 conflicts

0xe2307994…acad

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

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity