← previous blocknext block →recent activity
Analyzing
Block #98,655,649
36 transactions · 34 stateful · 2026-08-24 03:46:29 UTC
Parallelism
53/100
Blocked
68%
Avg conflicts / tx
4.17
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,655,649 · 36 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
3w05w06w110w011w112w213w314w416w217w018w119w220w321w422w523w624w725w826w927w1028w1129w12
- 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
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0xb0f831c0…fd80
0xa6afd3…d132
8 touches
6 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
8 touches
6 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0xb63ef486…0dcc
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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