← previous blocknext block →recent activity
Analyzing
Block #98,662,028
30 transactions · 28 stateful · 2026-08-24 04:19:48 UTC
Parallelism
43/100
Blocked
68%
Avg conflicts / tx
4.73
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,662,028 · 30 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w311w012w113w214w315w416w517w618w719w820w921w1022w1123w1224w1325w1426w1527w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
34 touches
136 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x11b69a7e…334e
0xee8c0e…1242
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x92c1f4a2…fead
0xa6afd3…d132
6 touches
3 conflicts
0xbddc67dc…1803
0x754704…b603
4 touches
1 conflict
0x27b6010e…e4aa
0x34b655…2a6f
2 touches
0 conflicts
0x2d151218…55f4
0x34b655…2a6f
2 touches
0 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: USDC (USDC)
136 conflicts on slot 0xd17580f913…78ece1
Audit this contract →
← previous block·next block →recent activity