← previous blocknext block →recent activity
Analyzing
Block #98,770,862
40 transactions · 27 stateful · 2026-08-24 13:33:37 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
1.02
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,770,862 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w611w714w419w735w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f663832…0647
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x17a7f697…dcb3
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: FastLane: FastLaneAuctionHandler
28 conflicts on slot 0x3f663832ed…a60647
Audit this contract →
← previous block·next block →recent activity