← previous blocknext block →recent activity

Analyzing

Block #85,175,553

22 transactions · 20 stateful · 2026-07-02 19:31:37 UTC

Parallelism

77/100

Blocked

40%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,175,553  ·  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

0x43e2eda1…396f

0x34b655…2a6f

8 touches
6 conflicts

0x51a914cf…a822

0x34b655…2a6f

8 touches
6 conflicts

0x2f23558a…8e0b

0x34b655…2a6f

8 touches
6 conflicts

0x74fd0a9b…3aaa

0x34b655…2a6f

8 touches
6 conflicts

0x9966da31…0d0f

0x34b655…2a6f

8 touches
6 conflicts

0xc9ce5af1…3c1c

0x34b655…2a6f

8 touches
6 conflicts

0xceb535f3…19cf

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

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity