← previous blocknext block →recent activity
Analyzing
Block #85,922,735
18 transactions · 14 stateful · 2026-07-06 06:28:50 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,922,735 · 18 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
3w04w15w06w07w114w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0x14f6fe51…1c24
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x32915b25…6070
0x34b655…2a6f
4 touches
1 conflict
0x35a9f06c…7689
0x34b655…2a6f
4 touches
1 conflict
0x62341e2a…2d78
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity