← previous blocknext block →recent activity
Analyzing
Block #86,958,158
22 transactions · 21 stateful · 2026-07-11 01:48:01 UTC
Parallelism
86/100
Blocked
19%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,958,158 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w111w117w018w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee4fe1f7…3ead
0x34b655…2a6f
6 touches
3 conflicts
0x1d8a34c1…fc67
0x34b655…2a6f
4 touches
1 conflict
0x236b16bf…ea47
0x34b655…2a6f
4 touches
1 conflict
0x44429a9b…771d
0x34b655…2a6f
4 touches
1 conflict
0x4caf91f9…8ab5
0x34b655…2a6f
4 touches
1 conflict
0x5bdaf996…8fef
0x34b655…2a6f
4 touches
1 conflict
0x5e67eb31…015a
0x34b655…2a6f
4 touches
1 conflict
0x5e67eb31…015b
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 0xee4fe1f73e…483ead
Audit this contract →
← previous block·next block →recent activity