← previous blocknext block →recent activity
Analyzing
Block #86,851,059
79 transactions · 63 stateful · 2026-07-10 13:52:05 UTC
Parallelism
70/100
Blocked
81%
Avg conflicts / tx
3.92
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #86,851,059 · 79 txs across 24 waves · depth 24
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
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w513w522w633w636w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
42 touches
210 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0x0e525f1d…dfed
0x34b655…2a6f
16 touches
28 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
16 touches
28 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
16 touches
28 conflicts
0xa07e7b13…7513
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
16 touches
28 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
210 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity