← previous blocknext block →recent activity
Analyzing
Block #86,612,308
36 transactions · 31 stateful · 2026-07-09 11:15:58 UTC
Parallelism
58/100
Blocked
71%
Avg conflicts / tx
2.47
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,612,308 · 36 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w16w27w08w110w011w112w013w114w215w316w417w518w619w720w821w922w1023w1124w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x7ce93f3d…b70e
0x34b655…2a6f
8 touches
6 conflicts
0x890eac6e…1c0d
0x34b655…2a6f
8 touches
6 conflicts
0x15a8dcd6…2c36
0x34b655…2a6f
6 touches
3 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
6 touches
3 conflicts
0x16784c1e…043f
0x34b655…2a6f
6 touches
3 conflicts
0x3b6e959d…158f
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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity