← previous blocknext block →recent activity
Analyzing
Block #95,472,145
48 transactions · 44 stateful · 2026-08-12 23:08:14 UTC
Parallelism
58/100
Blocked
80%
Avg conflicts / tx
3.5
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #95,472,145 · 48 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w08w19w210w311w412w513w328w1034w136w1637w1739w240w241w346w1847w19
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
18 touches
36 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
14 touches
21 conflicts
0xf1345bef…5530
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa3a621f8…75a2
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity