← previous blocknext block →recent activity
Analyzing
Block #98,839,581
24 transactions · 23 stateful · 2026-08-24 19:19:34 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,839,581 · 24 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
1w03w05w16w010w113w015w016w117w218w319w121w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51dc
0x69a5f9…2fef
8 touches
6 conflicts
0x2ef1d89b…196d
0x754704…b603
8 touches
6 conflicts
0x00000000…0036
0x35a73b…6042
8 touches
6 conflicts
0xaf831072…51d5
0x69a5f9…2fef
8 touches
6 conflicts
0xaf831072…51d6
0x69a5f9…2fef
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4c29ecd5…58b6
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…c551dc
Audit this contract →
← previous block·next block →recent activity