← previous blocknext block →recent activity
Analyzing
Block #98,273,361
32 transactions · 24 stateful · 2026-08-22 19:14:17 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,273,361 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w010w212w018w121w224w325w428w131w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae6b1bc5…7bb5
0xd32edf…ff58
9 touches
10 conflicts
0x4f4c191b…3458
0x065c9d…c394
5 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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
10 conflicts on slot 0xae6b1bc572…d27bb5
Audit this contract →
← previous block·next block →recent activity