← previous blocknext block →recent activity

Analyzing

Block #85,173,891

21 transactions · 20 stateful · 2026-07-02 19:20:32 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,173,891  ·  21 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

0x731e6d82…2883

0x065c9d…c394

6 touches
3 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x6d952553…8747

0x34b655…2a6f

6 touches
3 conflicts

0x74fd0a9b…3aaa

0x34b655…2a6f

6 touches
3 conflicts

0x801058a8…5bc3

0x34b655…2a6f

6 touches
3 conflicts

0xa00008a8…56dc

0x34b655…2a6f

6 touches
3 conflicts

0xa457c06e…2f06

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