← previous blocknext block →recent activity
Analyzing
Block #98,663,249
31 transactions · 29 stateful · 2026-08-24 04:26:12 UTC
Parallelism
45/100
Blocked
66%
Avg conflicts / tx
4.48
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #98,663,249 · 31 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
1w02w14w08w110w011w112w213w314w415w516w617w718w819w920w1021w1122w1223w1324w1425w1526w1628w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
34 touches
136 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x42daad7f…630b
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x92f41d1f…4258
0xa6afd3…d132
4 touches
1 conflict
0x68e5627d…6f8f
0x34b655…2a6f
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
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