← previous blocknext block →recent activity
Analyzing
Block #86,813,041
18 transactions · 17 stateful · 2026-07-10 09:37:49 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,813,041 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w410w012w113w216w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3ac1732…1dbb
0x34b655…2a6f
14 touches
21 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x74355ed1…eda6
0x34b655…2a6f
10 touches
10 conflicts
0x9966da31…0d0f
0x34b655…2a6f
10 touches
10 conflicts
0x9f40a209…1193
0x34b655…2a6f
10 touches
10 conflicts
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
21 conflicts on slot 0xc3ac173235…871dbb
Audit this contract →
← previous block·next block →recent activity