← previous blocknext block →recent activity
Analyzing
Block #94,485,334
25 transactions · 19 stateful · 2026-08-09 12:08:50 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
1.64
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #94,485,334 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w39w111w412w513w614w715w817w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f640b94…47bd
0xd32edf…ff58
17 touches
36 conflicts
0x6e890925…b0db
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd25997d0…a687
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
36 conflicts on slot 0x1f640b94b8…8c47bd
Audit this contract →
← previous block·next block →recent activity