← previous blocknext block →recent activity

Analyzing

Block #86,848,408

21 transactions · 19 stateful · 2026-07-10 13:34:22 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1.19

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,848,408  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x2130a548…c1de

0x34b655…2a6f

6 touches
3 conflicts

0x38c6ff01…689f

0x34b655…2a6f

6 touches
3 conflicts

0x19795ad6…4a16

0x34b655…2a6f

6 touches
3 conflicts

0x4e3abeff…18eb

0x34b655…2a6f

6 touches
3 conflicts

0x574628e9…dcc3

0x34b655…2a6f

6 touches
3 conflicts

0xe6e6f436…ddc0

0x34b655…2a6f

6 touches
3 conflicts

0x3230277c…ef39

0xc8689a…ee79

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