← previous blocknext block →recent activity
Analyzing
Block #86,835,936
66 transactions · 46 stateful · 2026-07-10 12:11:04 UTC
Parallelism
74/100
Blocked
80%
Avg conflicts / tx
2.2
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,835,936 · 66 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
1w02w13w14w26w27w08w112w313w014w117w220w321w443w246w348w449w550w652w753w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
12 touches
15 conflicts
0x74a7b40b…8922
0x34b655…2a6f
10 touches
10 conflicts
0x76ee219a…508f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 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