← previous blocknext block →recent activity

Analyzing

Block #85,160,325

20 transactions · 17 stateful · 2026-07-02 17:50:16 UTC

Parallelism

80/100

Blocked

35%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,160,325  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xcfa965cc…6fcf

0x34b655…2a6f

6 touches
3 conflicts

0xf324b405…ca30

0x34b655…2a6f

6 touches
3 conflicts

0x3c71ca9c…ed5c

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

0x34b655…2a6f

4 touches
1 conflict

0x63b15849…80b2

0x34b655…2a6f

4 touches
1 conflict

0x6fa99270…2038

0x34b655…2a6f

4 touches
1 conflict

0x7fffd49d…772a

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

6 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity