← previous blocknext block →recent activity
Analyzing
Block #86,955,739
20 transactions · 20 stateful · 2026-07-11 01:31:52 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,955,739 · 20 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
1w02w14w25w06w17w28w39w412w113w315w416w517w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
10 touches
10 conflicts
0x8a35acfb…d1ae
0xb1dbf0…c0d3
9 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0178c2de…b37d
0xb1dbf0…c0d3
6 touches
3 conflicts
0x74825c4e…32e9
0xb1dbf0…c0d3
6 touches
3 conflicts
0x737acb78…fce8
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity