← previous blocknext block →recent activity
Analyzing
Block #86,614,268
16 transactions · 14 stateful · 2026-07-09 11:29:04 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,614,268 · 16 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
2w04w05w16w27w38w410w115w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
7 touches
6 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
6 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0xfb4cb196…8c4a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x28227b6c…c740
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0004
0xb1dbf0…c0d3
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