← previous blocknext block →recent activity
Analyzing
Block #86,852,233
26 transactions · 13 stateful · 2026-07-10 13:59:56 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,852,233 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w010w112w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7fe04a…3c56
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8369620c…4792
0x34b655…2a6f
4 touches
1 conflict
0xa4e85e57…2567
0x34b655…2a6f
4 touches
1 conflict
0xbc7d5199…c05f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot 0xec7fe04ad1…2d3c56
Audit this contract →
← previous block·next block →recent activity