← previous blocknext block →recent activity
Analyzing
Block #86,855,069
107 transactions · 62 stateful · 2026-07-10 14:18:54 UTC
Parallelism
86/100
Blocked
76%
Avg conflicts / tx
2.38
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,855,069 · 107 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
4w05w18w29w310w411w527w129w230w332w433w535w636w738w839w941w1042w1176w677w778w884w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
26 touches
78 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
26 touches
78 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
26 touches
78 conflicts
0xa07e7b13…7513
0x34b655…2a6f
26 touches
78 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
26 touches
78 conflicts
0xf94d24c1…5f81
0x34b655…2a6f
26 touches
78 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
24 touches
66 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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity