← previous blocknext block →recent activity
Analyzing
Block #86,807,931
15 transactions · 14 stateful · 2026-07-10 09:03:39 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,807,931 · 15 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
5w08w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
6 touches
3 conflicts
0x1d84bebc…07d0
0x34b655…2a6f
4 touches
1 conflict
0x8eef368f…aa21
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x50dfdd6a…fc6a
0x34b655…2a6f
4 touches
1 conflict
0x1d84bebc…07d1
0x34b655…2a6f
4 touches
1 conflict
0x1a0c3cc5…6c5a
0x754704…b603
2 touches
0 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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity