← previous blocknext block →recent activity

Analyzing

Block #85,132,372

21 transactions · 18 stateful · 2026-07-02 14:44:01 UTC

Parallelism

67/100

Blocked

61%

Avg conflicts / tx

1.67

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,132,372  ·  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

14 touches
21 conflicts

0xe47478a3…a058

0x34b655…2a6f

14 touches
21 conflicts

0x366f651e…6100

0x34b655…2a6f

12 touches
15 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

12 touches
15 conflicts

0x922c7ebd…6600

0xc8689a…ee79

12 touches
15 conflicts

0x7ae63663…9d94

0x34b655…2a6f

12 touches
15 conflicts

0x97c67486…27fe

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 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