← previous blocknext block →recent activity
Analyzing
Block #98,940,787
20 transactions · 20 stateful · 2026-08-25 03:48:42 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,940,787 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w010w011w112w213w314w418w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51d6
0x69a5f9…2fef
10 touches
10 conflicts
0xaf831072…51dc
0x69a5f9…2fef
10 touches
10 conflicts
0x2ef1d89b…196d
0x754704…b603
10 touches
10 conflicts
0xfda39b6f…d4cc
0x754704…b603
10 touches
10 conflicts
0x00000000…0036
0x35a73b…6042
10 touches
10 conflicts
0xaf831072…51d5
0x69a5f9…2fef
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
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
10 conflicts on slot 0xaf831072f6…c551d6
Audit this contract →
← previous block·next block →recent activity