← previous blocknext block →recent activity
Analyzing
Block #98,677,665
36 transactions · 22 stateful · 2026-08-24 05:41:17 UTC
Parallelism
92/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,677,665 · 36 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w08w011w012w013w120w123w024w125w227w128w230w132w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefeb7937…c283
0x34b655…2a6f
6 touches
3 conflicts
0x67b39109…a986
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xf48e6329…f7bf
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x065ff70b…356d
0x40c49f…2af0
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
3 conflicts on slot 0xefeb793761…25c283
Audit this contract →
← previous block·next block →recent activity