← previous blocknext block →recent activity
Analyzing
Block #99,251,382
16 transactions · 14 stateful · 2026-08-26 05:58:05 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,251,382 · 16 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
1w02w16w27w39w010w112w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fbc0ef1…e5f7
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xa10cca85…0952
0x754704…b603
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
10 conflicts on slot 0x0fbc0ef124…c6e5f7
Audit this contract →
← previous block·next block →recent activity