← previous blocknext block →recent activity
Analyzing
Block #87,687,980
20 transactions · 18 stateful · 2026-07-14 11:08:32 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,687,980 · 20 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
1w03w16w07w08w19w213w314w418w019w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x70b7b52e…7743
0x34b655…2a6f
6 touches
3 conflicts
0x70b7b52e…7744
0x34b655…2a6f
6 touches
3 conflicts
0x6446a0c9…f422
0x34b655…2a6f
4 touches
1 conflict
0x7118f456…6083
0x34b655…2a6f
4 touches
1 conflict
0x71604178…a3a8
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