← previous blocknext block →recent activity
Analyzing
Block #87,049,171
10 transactions · 9 stateful · 2026-07-11 11:56:13 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,049,171 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xa248a5dd…4a69
0x34b655…2a6f
4 touches
1 conflict
0x1d61ab3f…1516
0x34b655…2a6f
2 touches
0 conflicts
0x426e1f22…5ff9
0x34b655…2a6f
2 touches
0 conflicts
0x4ff21e31…8ed4
0x34b655…2a6f
2 touches
0 conflicts
0x66f7b1ee…a38b
0x34b655…2a6f
2 touches
0 conflicts
0x85ebc5d3…fdd8
0x34b655…2a6f
2 touches
0 conflicts
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity