← previous blocknext block →recent activity
Analyzing
Block #99,488,502
24 transactions · 20 stateful · 2026-08-27 01:51:52 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,488,502 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w08w09w111w112w213w014w315w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5f66002…809d
0xd32edf…ff58
7 touches
6 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xd25997d0…a683
0x1b6862…e19c
4 touches
1 conflict
0x00500a94…20d5
0x34b655…2a6f
4 touches
1 conflict
0x34de6bae…7a7c
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x801a6e57…d85c
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: FastLane: FastLaneAuctionHandler
6 conflicts on slot 0xf5f6600239…52809d
Audit this contract →
← previous block·next block →recent activity