← previous blocknext block →recent activity
Analyzing
Block #96,708,224
13 transactions · 12 stateful · 2026-08-17 06:47:10 UTC
Parallelism
46/100
Blocked
50%
Avg conflicts / tx
1.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,708,224 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x966e45cf…0f25
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x667407f5…720f
0x34b655…2a6f
6 touches
3 conflicts
0xcf501ad8…99ed
0x34b655…2a6f
6 touches
3 conflicts
0xf30b9357…2e1e
0x34b655…2a6f
6 touches
3 conflicts
0x98cfeec2…d6e5
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity