← previous blocknext block →recent activity
Analyzing
Block #87,333,233
20 transactions · 18 stateful · 2026-07-12 19:35:39 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,333,233 · 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
2w05w16w27w38w011w112w216w017w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ea6a117…f2f2
0x34b655…2a6f
8 touches
6 conflicts
0xffb8950c…23c6
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x924bac95…3f39
0x34b655…2a6f
6 touches
3 conflicts
0x94bc4690…79be
0x34b655…2a6f
6 touches
3 conflicts
0xa8b18ba0…f380
0x34b655…2a6f
6 touches
3 conflicts
0xb835d684…089c
0x34b655…2a6f
6 touches
3 conflicts
0xd064a456…b881
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0x7ea6a11745…1df2f2
Audit this contract →
← previous block·next block →recent activity