← previous blocknext block →recent activity
Analyzing
Block #86,847,758
48 transactions · 39 stateful · 2026-07-10 13:30:01 UTC
Parallelism
67/100
Blocked
49%
Avg conflicts / tx
1.38
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,847,758 · 48 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w110w011w112w213w314w415w516w624w125w226w727w831w942w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xfdde6236…b2a5
0x34b655…2a6f
12 touches
15 conflicts
0xd8de9f79…53bd
0x34b655…2a6f
12 touches
15 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
10 touches
10 conflicts
0x380c75ae…cfe6
0x34b655…2a6f
10 touches
10 conflicts
0x5fee1ba0…2520
0x34b655…2a6f
10 touches
10 conflicts
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 conflicts
0x6f42e42b…5717
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity