← previous blocknext block →recent activity
Analyzing
Block #86,798,404
57 transactions · 44 stateful · 2026-07-10 08:00:00 UTC
Parallelism
68/100
Blocked
73%
Avg conflicts / tx
2.21
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,798,404 · 57 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w28w39w410w116w017w119w220w321w422w523w624w725w834w235w439w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
16 touches
28 conflicts
0xfc24540b…6463
0x34b655…2a6f
16 touches
28 conflicts
0xd7668c61…55f8
0x34b655…2a6f
16 touches
28 conflicts
0x3230277c…ef39
0xc8689a…ee79
16 touches
28 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
16 touches
28 conflicts
0xd6113c0f…0a4b
0x34b655…2a6f
14 touches
21 conflicts
0x47be1402…75f4
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
55 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity