← previous blocknext block →recent activity
Analyzing
Block #86,907,178
24 transactions · 20 stateful · 2026-07-10 20:07:27 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,907,178 · 24 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
6w07w18w29w314w015w016w417w521w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x98d58911…19f2
0x34b655…2a6f
8 touches
6 conflicts
0xed660153…a905
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0x7da56943…9753
0x34b655…2a6f
6 touches
3 conflicts
0x23876918…de57
0x34b655…2a6f
6 touches
3 conflicts
0x2e9cbcb5…6152
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity