← previous blocknext block →recent activity

Analyzing

Block #85,162,231

27 transactions · 21 stateful · 2026-07-02 18:02:58 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,162,231  ·  27 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

12 touches
15 conflicts

0x3ea25e92…a36d

0x34b655…2a6f

6 touches
3 conflicts

0xa678cd56…4fab

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xbc8ead31…90fd

0x34b655…2a6f

6 touches
3 conflicts

0xd2862d04…388c

0x34b655…2a6f

6 touches
3 conflicts

0x6167486f…db40

0x34b655…2a6f

6 touches
3 conflicts

0x87dade3f…7182

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