← previous blocknext block →recent activity
Analyzing
Block #95,022,282
34 transactions · 29 stateful · 2026-08-11 09:11:04 UTC
Parallelism
50/100
Blocked
72%
Avg conflicts / tx
2.91
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #95,022,282 · 34 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
1w02w13w24w35w210w411w512w613w718w820w923w1025w1128w1229w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
20 touches
45 conflicts
0x00000000…00c9
0x34b655…2a6f
16 touches
28 conflicts
0x775a8ad3…8307
0x34b655…2a6f
14 touches
21 conflicts
0xd3edd657…17cd
0x34b655…2a6f
14 touches
21 conflicts
0x842dd93b…a41f
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4a3
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4b2
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
45 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity