← previous blocknext block →recent activity

Analyzing

Block #85,139,873

22 transactions · 22 stateful · 2026-07-02 15:34:05 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,139,873  ·  22 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

0xaa48195d…ffee

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x67d8b378…f2f8

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x264f7d7d…8444

0x34b655…2a6f

6 touches
3 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

6 touches
3 conflicts

0xa0efa7bc…8b24

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

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity