← previous blocknext block →recent activity
Analyzing
Block #86,767,352
56 transactions · 46 stateful · 2026-07-10 04:32:43 UTC
Parallelism
61/100
Blocked
85%
Avg conflicts / tx
4.54
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #86,767,352 · 56 txs across 22 waves · depth 22
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
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w29w310w413w514w619w144w447w549w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
36 touches
153 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
14 touches
21 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
14 touches
21 conflicts
0xbd7d184b…61f1
0x34b655…2a6f
14 touches
21 conflicts
0x94e7f277…471b
0x34b655…2a6f
12 touches
15 conflicts
0xa121613d…91db
0x34b655…2a6f
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
153 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity