← previous blocknext block →recent activity
Analyzing
Block #86,564,025
30 transactions · 22 stateful · 2026-07-09 05:52:08 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,564,025 · 30 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
1w02w13w24w36w07w18w29w310w412w113w417w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x0b2e7865…50e4
0xd32edf…ff58
9 touches
10 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0xd064a456…b881
0x34b655…2a6f
8 touches
6 conflicts
0xdc921364…4680
0x34b655…2a6f
8 touches
6 conflicts
0xe6d4c76c…2179
0x34b655…2a6f
8 touches
6 conflicts
0xe727ab72…768b
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity