← previous blocknext block →recent activity
Analyzing
Block #96,604,572
30 transactions · 29 stateful · 2026-08-16 22:05:52 UTC
Parallelism
43/100
Blocked
66%
Avg conflicts / tx
4
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #96,604,572 · 30 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
1w02w03w04w16w17w210w311w412w513w614w715w816w917w1018w1121w1023w1224w1327w1428w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x4caa7900…fd2e
0x34b655…2a6f
10 touches
10 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
10 touches
10 conflicts
0x2d651956…12e8
0x34b655…2a6f
10 touches
10 conflicts
0x0f6aef87…8137
0x34b655…2a6f
8 touches
6 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity