← previous blocknext block →recent activity
Analyzing
Block #86,957,904
62 transactions · 44 stateful · 2026-07-11 01:46:19 UTC
Parallelism
65/100
Blocked
84%
Avg conflicts / tx
3.79
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #86,957,904 · 62 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
1w02w13w28w313w416w519w620w721w850w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0xb0446875…2b96
0x34b655…2a6f
20 touches
45 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x2b268fa9…eba2
0x34b655…2a6f
16 touches
28 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
16 touches
28 conflicts
0x826cce18…251c
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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity