← previous blocknext block →recent activity
Analyzing
Block #85,123,422
24 transactions · 22 stateful · 2026-07-02 13:44:11 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,123,422 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w06w17w29w010w111w212w313w421w022w123w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40b5f387…a164
0x34b655…2a6f
10 touches
10 conflicts
0x548145a9…cfce
0x34b655…2a6f
10 touches
10 conflicts
0x63b15849…80b2
0x34b655…2a6f
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xe47478a3…a058
0x34b655…2a6f
10 touches
10 conflicts
0x2ff8d4c8…9666
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 0x40b5f38715…7ba164
Audit this contract →
← previous block·next block →recent activity