← previous blocknext block →recent activity

Analyzing

Block #85,125,936

25 transactions · 18 stateful · 2026-07-02 14:00:59 UTC

Parallelism

88/100

Blocked

33%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,125,936  ·  25 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x0d748d21…eede

0x34b655…2a6f

4 touches
1 conflict

0x1e7e4246…4872

0x34b655…2a6f

4 touches
1 conflict

0x286711a5…b3bf

0x34b655…2a6f

4 touches
1 conflict

0x3e505a15…70f8

0x34b655…2a6f

4 touches
1 conflict

0x4384dd01…4f99

0x34b655…2a6f

4 touches
1 conflict

0x4a4dc019…a2fb

0x34b655…2a6f

4 touches
1 conflict

0x6db97e95…8353

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity