← previous blocknext block →recent activity
Analyzing
Block #86,661,268
17 transactions · 14 stateful · 2026-07-09 16:44:18 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,661,268 · 17 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
3w04w15w07w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8f6f7a3…f563
0x34b655…2a6f
6 touches
3 conflicts
0x322dcd34…8718
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc8f6f7a3…f564
0x34b655…2a6f
6 touches
3 conflicts
0x5138188e…796b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8e9aaa9b…c434
0x34b655…2a6f
4 touches
1 conflict
0x901f4dfc…1ba4
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 0xc8f6f7a3f3…78f563
Audit this contract →
← previous block·next block →recent activity