← previous blocknext block →recent activity
Analyzing
Block #86,711,901
28 transactions · 19 stateful · 2026-07-09 22:22:09 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,711,901 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w113w214w015w116w220w322w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
5 touches
3 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
5 touches
3 conflicts
0x6c68ddc9…d106
0xb1dbf0…c0d3
5 touches
3 conflicts
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7f2141d6…42bd
0x34b655…2a6f
4 touches
1 conflict
0x813d6148…7e8f
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity