← previous blocknext block →recent activity
Analyzing
Block #86,674,412
54 transactions · 45 stateful · 2026-07-09 18:12:01 UTC
Parallelism
69/100
Blocked
73%
Avg conflicts / tx
3.04
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,674,412 · 54 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
1w02w03w16w17w29w210w311w012w113w214w318w019w120w221w322w423w524w636w341w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
28 touches
91 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x503b3a72…f6df
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x25de453d…9573
0x34b655…2a6f
10 touches
10 conflicts
0x620b761c…270e
0x34b655…2a6f
8 touches
6 conflicts
0x65338476…2209
0x34b655…2a6f
8 touches
6 conflicts
0x656bd53e…af4e
0x34b655…2a6f
8 touches
6 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
91 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity