← previous blocknext block →recent activity
Analyzing
Block #98,740,043
20 transactions · 17 stateful · 2026-08-24 10:58:27 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,740,043 · 20 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
1w05w17w08w111w212w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5afd2c6b…7bef
0xd32edf…ff58
7 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x4245e4e8…096e
0x000000…012a
2 touches
0 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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: FastLane: FastLaneAuctionHandler
6 conflicts on slot 0x5afd2c6b65…e57bef
Audit this contract →
← previous block·next block →recent activity