← previous blocknext block →recent activity
Analyzing
Block #98,658,363
37 transactions · 34 stateful · 2026-08-24 04:00:41 UTC
Parallelism
54/100
Blocked
74%
Avg conflicts / tx
4.11
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,658,363 · 37 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
1w04w05w17w08w19w210w311w413w114w215w016w117w218w319w420w521w622w723w824w925w1033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
34 touches
136 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xa1665792…c63b
0xa6afd3…d132
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xc20f02b1…bcb3
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: USDC (USDC)
136 conflicts on slot 0xd17580f913…78ece1
Audit this contract →
← previous block·next block →recent activity