← previous blocknext block →recent activity
Analyzing
Block #94,741,736
34 transactions · 27 stateful · 2026-08-10 09:39:04 UTC
Parallelism
85/100
Blocked
44%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,741,736 · 34 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
1w02w04w16w08w111w114w015w116w217w318w426w127w229w230w031w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad432a63…d137
0xd32edf…ff58
9 touches
10 conflicts
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0xd5a25205…6458
0x1b6862…e19c
6 touches
3 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
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
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 0xad432a634d…dfd137
Audit this contract →
← previous block·next block →recent activity