← previous blocknext block →recent activity
Analyzing
Block #85,158,841
22 transactions · 17 stateful · 2026-07-02 17:40:27 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,158,841 · 22 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
2w03w16w07w18w29w310w413w214w318w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x06aed19e…ca57
0x34b655…2a6f
4 touches
1 conflict
0x159b8597…48a4
0x34b655…2a6f
4 touches
1 conflict
0x22cd3f83…a62c
0x34b655…2a6f
4 touches
1 conflict
0x261fe721…3ca8
0x34b655…2a6f
4 touches
1 conflict
0x3149127f…19a9
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity