← previous blocknext block →recent activity
Analyzing
Block #87,733,958
19 transactions · 19 stateful · 2026-07-14 16:16:28 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,733,958 · 19 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
4w05w16w07w110w211w314w418w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2dde3f33…5b65
0x34b655…2a6f
6 touches
3 conflicts
0x5eb5d9be…b2c1
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbf0e051a…10a0
0x34b655…2a6f
6 touches
3 conflicts
0xf0571291…b6ca
0x34b655…2a6f
6 touches
3 conflicts
0x612b169a…b2e5
0x34b655…2a6f
4 touches
1 conflict
0x307414a5…7214
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity