← previous blocknext block →recent activity
Analyzing
Block #86,793,232
24 transactions · 20 stateful · 2026-07-10 07:25:27 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,793,232 · 24 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
1w02w15w06w111w214w015w116w220w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x9c4f8459…b171
0xd32edf…ff58
5 touches
3 conflicts
0x5296a598…5661
0x34b655…2a6f
4 touches
1 conflict
0x6d105005…3cc9
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
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
6 conflicts on slot 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity