← previous blocknext block →recent activity
Analyzing
Block #85,535,412
23 transactions · 19 stateful · 2026-07-04 11:28:09 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,535,412 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w19w010w111w212w313w314w417w418w120w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea4316bc…6b4f
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x3230277c…ef39
0xc8689a…ee79
6 touches
3 conflicts
0x89999c15…fdac
0x34b655…2a6f
6 touches
3 conflicts
0xa435dee8…f2be
0x34b655…2a6f
6 touches
3 conflicts
0xcd81cc7b…8da0
0x34b655…2a6f
6 touches
3 conflicts
0x7629505e…e0a1
0x34b655…2a6f
4 touches
1 conflict
0x2656e998…6540
0x40c49f…2af0
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
10 conflicts on slot 0xea4316bcc7…a66b4f
Audit this contract →
← previous block·next block →recent activity