← previous blocknext block →recent activity
Analyzing
Block #86,625,126
21 transactions · 19 stateful · 2026-07-09 12:41:31 UTC
Parallelism
76/100
Blocked
26%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,625,126 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w111w212w313w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6aef87…8137
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb07a0849…3b62
0xb1dbf0…c0d3
4 touches
1 conflict
0x0ff1ee46…0c08
0x34b655…2a6f
4 touches
1 conflict
0x56153262…21ce
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x0f6aef8771…dd8137
Audit this contract →
← previous block·next block →recent activity