← previous blocknext block →recent activity
Analyzing
Block #86,623,238
53 transactions · 37 stateful · 2026-07-09 12:28:57 UTC
Parallelism
68/100
Blocked
76%
Avg conflicts / tx
2.47
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,623,238 · 53 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w07w19w212w314w015w316w422w023w124w225w326w427w538w540w543w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
28 touches
91 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
16 touches
28 conflicts
0x076fc848…5c81
0x34b655…2a6f
14 touches
21 conflicts
0x3230277c…ef39
0xc8689a…ee79
14 touches
21 conflicts
0x2c2761c0…476e
0x34b655…2a6f
14 touches
21 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
14 touches
21 conflicts
0x53a6519e…732e
0x34b655…2a6f
14 touches
21 conflicts
0x5fad6fee…7714
0x34b655…2a6f
14 touches
21 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
91 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity