← previous blocknext block →recent activity
Analyzing
Block #91,418,317
21 transactions · 14 stateful · 2026-07-29 18:43:48 UTC
Parallelism
76/100
Blocked
57%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,418,317 · 21 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
1w05w16w27w311w012w113w114w415w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae7f39cf…2f3f
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x14d1bf0e…e0a0
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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 0xae7f39cf3d…942f3f
Audit this contract →
← previous block·next block →recent activity