← previous blocknext block →recent activity
Analyzing
Block #99,091,199
33 transactions · 29 stateful · 2026-08-25 16:32:04 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,091,199 · 33 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
2w04w07w09w110w211w312w416w020w123w124w125w229w030w131w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70051a8d…e637
0xd32edf…ff58
9 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x1f8a126c…9aa1
0x1b6862…e19c
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 0x70051a8d0c…71e637
Audit this contract →
← previous block·next block →recent activity