← previous blocknext block →recent activity
Analyzing
Block #87,058,191
14 transactions · 13 stateful · 2026-07-11 12:56:28 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,058,191 · 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
3w04w16w07w29w010w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebd8c9b0…2ba6
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x23778a1f…dec4
0x34b655…2a6f
4 touches
1 conflict
0x2ba767bb…0efa
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x388633a0…86cd
0x34b655…2a6f
4 touches
1 conflict
0x3ae90d94…cfba
0x34b655…2a6f
4 touches
1 conflict
0x43603f1e…c190
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 0xebd8c9b046…352ba6
Audit this contract →
← previous block·next block →recent activity