← previous blocknext block →recent activity
Analyzing
Block #98,663,595
36 transactions · 34 stateful · 2026-08-24 04:27:59 UTC
Parallelism
56/100
Blocked
59%
Avg conflicts / tx
3.5
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,663,595 · 36 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w19w114w115w218w019w120w221w322w423w524w625w726w827w928w1029w1130w1231w1332w1433w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
32 touches
120 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x27b6010e…e4aa
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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: USDC (USDC)
120 conflicts on slot 0xd17580f913…78ece1
Audit this contract →
← previous block·next block →recent activity