← previous blocknext block →recent activity
Analyzing
Block #98,843,032
21 transactions · 20 stateful · 2026-08-24 19:36:56 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,843,032 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w011w012w113w214w315w416w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51d6
0x69a5f9…2fef
12 touches
15 conflicts
0xaf831072…51dc
0x69a5f9…2fef
12 touches
15 conflicts
0x2ef1d89b…196d
0x754704…b603
12 touches
15 conflicts
0x00000000…0036
0x35a73b…6042
12 touches
15 conflicts
0xaf831072…51d5
0x69a5f9…2fef
12 touches
15 conflicts
0x41be9e75…9773
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
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: 0x69a5f9ad…102fef
15 conflicts on slot 0xaf831072f6…c551d6
Audit this contract →
← previous block·next block →recent activity