← previous blocknext block →recent activity
Analyzing
Block #95,781,765
56 transactions · 52 stateful · 2026-08-14 01:06:35 UTC
Parallelism
66/100
Blocked
81%
Avg conflicts / tx
3.16
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #95,781,765 · 56 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w17w29w310w011w114w123w625w834w1238w1340w241w142w343w444w446w247w348w549w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x734ee320…caae
0x34b655…2a6f
12 touches
15 conflicts
0x08636046…e60f
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
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
36 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity