← previous blocknext block →recent activity
Analyzing
Block #98,383,183
12 transactions · 12 stateful · 2026-08-23 04:26:50 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,383,183 · 12 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
1w04w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4c9a0df…dcd4
0x34b655…2a6f
6 touches
3 conflicts
0x074c08f8…fb56
0x34b655…2a6f
4 touches
1 conflict
0x9ad68d6f…bca7
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf269bae…b57b
0x34b655…2a6f
4 touches
1 conflict
0xe78512ae…d4ff
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd5
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
3 conflicts on slot 0xf4c9a0dfc5…fcdcd4
Audit this contract →
← previous block·next block →recent activity