← previous blocknext block →recent activity
Analyzing
Block #87,352,258
14 transactions · 13 stateful · 2026-07-12 21:42:50 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,352,258 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68761f35…6026
0x34b655…2a6f
6 touches
3 conflicts
0x6f761690…95bd
0x34b655…2a6f
6 touches
3 conflicts
0x3c7908ed…47c8
0x34b655…2a6f
6 touches
3 conflicts
0x7ec6c8db…23b0
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x35d95fb0…db9f
0x34b655…2a6f
4 touches
1 conflict
0x48d43dc8…8d00
0x34b655…2a6f
4 touches
1 conflict
0x5d36316b…b0e4
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 0x68761f355d…c46026
Audit this contract →
← previous block·next block →recent activity