← previous blocknext block →recent activity
Analyzing
Block #95,152,923
67 transactions · 53 stateful · 2026-08-11 20:09:02 UTC
Parallelism
67/100
Blocked
83%
Avg conflicts / tx
3.48
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #95,152,923 · 67 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
1w02w03w14w25w36w47w531w152w553w654w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
18 touches
36 conflicts
0xafb8e71e…9285
0x34b655…2a6f
18 touches
36 conflicts
0xec7d120d…7084
0x34b655…2a6f
14 touches
21 conflicts
0xbe9baf16…df37
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity