← previous blocknext block →recent activity
Analyzing
Block #86,734,040
17 transactions · 14 stateful · 2026-07-10 00:50:06 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,734,040 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w09w111w213w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x9a287655…f785
0x34b655…2a6f
6 touches
3 conflicts
0x0d43cc69…6f83
0x34b655…2a6f
6 touches
3 conflicts
0xb7b28ab0…40d1
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xfeacfacd…41d2
0x34b655…2a6f
6 touches
3 conflicts
0x3b787279…727f
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity