← previous blocknext block →recent activity
Analyzing
Block #85,349,968
27 transactions · 22 stateful · 2026-07-03 14:53:27 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,349,968 · 27 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
1w03w14w05w16w07w18w29w016w317w421w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3f24a374…6bc3
0x34b655…2a6f
4 touches
1 conflict
0x4227fcc7…ba68
0x34b655…2a6f
4 touches
1 conflict
0x57bb625a…286d
0x34b655…2a6f
4 touches
1 conflict
0x5efa0d16…4a5d
0x34b655…2a6f
4 touches
1 conflict
0x9966da31…0d0f
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
Audit this contract →
← previous block·next block →recent activity