← previous blocknext block →recent activity
Analyzing
Block #98,664,240
52 transactions · 49 stateful · 2026-08-24 04:31:19 UTC
Parallelism
62/100
Blocked
69%
Avg conflicts / tx
4.31
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #98,664,240 · 52 txs across 20 waves · depth 20
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
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w06w18w114w015w116w117w218w319w420w524w025w026w145w250w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
40 touches
190 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x34533f60…70ae
0xa6afd3…d132
10 touches
10 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
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: USDC (USDC)
190 conflicts on slot 0xd17580f913…78ece1
Audit this contract →
← previous block·next block →recent activity