← previous blocknext block →recent activity
Analyzing
Block #96,317,333
25 transactions · 24 stateful · 2026-08-15 22:00:53 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,317,333 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w414w416w517w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x0b652521…d6df
0x34b655…2a6f
6 touches
3 conflicts
0x705ab4ae…0162
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xf40e9839…0001
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity