← previous blocknext block →recent activity
Analyzing
Block #98,839,812
18 transactions · 17 stateful · 2026-08-24 19:20:44 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,839,812 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w19w010w111w212w313w214w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51d5
0x69a5f9…2fef
8 touches
6 conflicts
0xaf831072…51dc
0x69a5f9…2fef
8 touches
6 conflicts
0x2ef1d89b…196d
0x754704…b603
8 touches
6 conflicts
0xaf831072…51d6
0x69a5f9…2fef
8 touches
6 conflicts
0xfda39b6f…d4cc
0x754704…b603
8 touches
6 conflicts
0x00000000…0036
0x35a73b…6042
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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: 0x69a5f9ad…102fef
6 conflicts on slot 0xaf831072f6…c551d5
Audit this contract →
← previous block·next block →recent activity