← previous blocknext block →recent activity
Analyzing
Block #86,959,592
39 transactions · 38 stateful · 2026-07-11 01:57:37 UTC
Parallelism
51/100
Blocked
71%
Avg conflicts / tx
3.05
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #86,959,592 · 39 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w17w28w09w110w211w212w013w114w215w316w417w518w619w720w826w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x6e942750…9953
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x727fbce7…0c80
0x34b655…2a6f
12 touches
15 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
12 touches
15 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
12 touches
15 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity