← previous blocknext block →recent activity
Analyzing
Block #87,667,095
24 transactions · 21 stateful · 2026-07-14 08:48:57 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,667,095 · 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
6w07w09w112w213w015w116w317w418w520w021w123w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xfb4cb196…8c4a
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
6 touches
3 conflicts
0x426e1f22…5ff9
0x34b655…2a6f
6 touches
3 conflicts
0x6280c6c6…11ac
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x87170ee5…7094
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity