← previous blocknext block →recent activity
Analyzing
Block #87,703,933
19 transactions · 19 stateful · 2026-07-14 12:55:24 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,703,933 · 19 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
3w04w18w09w110w211w313w014w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f556856…2916
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x354afb1d…2b3c
0x34b655…2a6f
4 touches
1 conflict
0x435b08b5…d84e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f51d069…d0b4
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
6 conflicts on slot 0x0f5568567b…4b2916
Audit this contract →
← previous block·next block →recent activity