← previous blocknext block →recent activity
Analyzing
Block #98,848,191
18 transactions · 16 stateful · 2026-08-24 20:02:53 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,848,191 · 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
1w02w13w25w09w010w111w212w313w114w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0036
0x35a73b…6042
8 touches
6 conflicts
0xaf831072…51d6
0x69a5f9…2fef
8 touches
6 conflicts
0xaf831072…51dc
0x69a5f9…2fef
8 touches
6 conflicts
0x2ef1d89b…196d
0x754704…b603
8 touches
6 conflicts
0xaf831072…51d5
0x69a5f9…2fef
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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: 0x35a73bac…1d6042
6 conflicts on slot 0x0000000000…000036
Audit this contract →
← previous block·next block →recent activity