← previous blocknext block →recent activity
Analyzing
Block #86,673,777
73 transactions · 52 stateful · 2026-07-09 18:07:47 UTC
Parallelism
67/100
Blocked
79%
Avg conflicts / tx
3.78
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #86,673,777 · 73 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
2w07w08w19w210w311w414w517w627w155w460w561w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
38 touches
171 conflicts
0xb5d00374…1d2a
0x34b655…2a6f
18 touches
36 conflicts
0x459573ed…fbbe
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x2029b74e…c206
0x34b655…2a6f
14 touches
21 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xd1832cbf…1761
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
171 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity