← previous blocknext block →recent activity
Analyzing
Block #87,761,194
20 transactions · 18 stateful · 2026-07-14 19:18:37 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
1.4
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,761,194 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w29w310w412w513w614w715w817w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0x255ba9f3…396d
0x34b655…2a6f
10 touches
10 conflicts
0x147259c6…1709
0x34b655…2a6f
10 touches
10 conflicts
0xe8706f47…bacf
0x34b655…2a6f
6 touches
3 conflicts
0x3d22c439…de6d
0x34b655…2a6f
6 touches
3 conflicts
0x84835cf9…fb40
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity