← previous blocknext block →recent activity
Analyzing
Block #86,958,974
34 transactions · 27 stateful · 2026-07-11 01:53:29 UTC
Parallelism
88/100
Blocked
26%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,958,974 · 34 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
1w02w04w19w111w121w022w125w026w027w228w129w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x9355efee…7bcd
0x34b655…2a6f
6 touches
3 conflicts
0x288961aa…ac7f
0x34b655…2a6f
6 touches
3 conflicts
0x6f8d1316…b303
0x34b655…2a6f
4 touches
1 conflict
0xdc1b8d30…5eda
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity