← previous blocknext block →recent activity

Analyzing

Block #86,495,689

18 transactions · 18 stateful · 2026-07-08 22:15:01 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,495,689  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xa1571d54…ae41

0x34b655…2a6f

8 touches
6 conflicts

0xabe6c059…07f2

0x34b655…2a6f

8 touches
6 conflicts

0x88dfc211…169a

0x34b655…2a6f

8 touches
6 conflicts

0x3d4584df…ffed

0x34b655…2a6f

8 touches
6 conflicts

0x511ecf07…8ed0

0x34b655…2a6f

8 touches
6 conflicts

0x06aed19e…ca57

0x34b655…2a6f

8 touches
6 conflicts

0x0e9a70ab…e67c

0x34b655…2a6f

8 touches
6 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

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity