← previous blocknext block →recent activity
Analyzing
Block #87,589,566
21 transactions · 20 stateful · 2026-07-14 00:10:42 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,589,566 · 21 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
2w04w05w16w29w111w112w313w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa534ab65…4ee7
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x38e39eef…50bd
0x34b655…2a6f
4 touches
1 conflict
0x43cea534…ddce
0x34b655…2a6f
4 touches
1 conflict
0x4467ecee…e95b
0x34b655…2a6f
4 touches
1 conflict
0x8d1f7216…affc
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 0xa534ab6553…be4ee7
Audit this contract →
← previous block·next block →recent activity