← previous blocknext block →recent activity
Analyzing
Block #86,776,405
18 transactions · 14 stateful · 2026-07-10 05:33:10 UTC
Parallelism
78/100
Blocked
21%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,776,405 · 18 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
5w07w08w110w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b6c252d…a696
0x34b655…2a6f
6 touches
3 conflicts
0xa37e64f8…ba05
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdb3774c5…2442
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7c7eff13…16db
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a59
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a5a
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 0x7b6c252d22…b1a696
Audit this contract →
← previous block·next block →recent activity