← previous blocknext block →recent activity

Analyzing

Block #85,145,636

22 transactions · 21 stateful · 2026-07-02 16:12:30 UTC

Parallelism

64/100

Blocked

71%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #85,145,636  ·  22 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

0x67d8b378…f2f8

0x34b655…2a6f

8 touches
6 conflicts

0x9966da31…0d0f

0x34b655…2a6f

8 touches
6 conflicts

0xa44cb9b7…c5a8

0x34b655…2a6f

8 touches
6 conflicts

0xd2a592d9…1a96

0x34b655…2a6f

8 touches
6 conflicts

0xe732567d…b65d

0x34b655…2a6f

8 touches
6 conflicts

0xecbd9ae6…6688

0x34b655…2a6f

8 touches
6 conflicts

0xf7e59d30…11dd

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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity