← previous blocknext block →recent activity
Analyzing
Block #86,683,692
17 transactions · 16 stateful · 2026-07-09 19:13:59 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,683,692 · 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
1w04w05w18w19w210w311w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0x5e4154c7…a40b
0x34b655…2a6f
4 touches
1 conflict
0x6a17cb09…3ff0
0x34b655…2a6f
4 touches
1 conflict
0x7f2141d6…42bd
0x34b655…2a6f
4 touches
1 conflict
0x7fe5f42f…a5b3
0x34b655…2a6f
4 touches
1 conflict
0x8fa1ba4f…a56f
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity