← previous blocknext block →recent activity
Analyzing
Block #94,869,917
20 transactions · 17 stateful · 2026-08-10 20:24:43 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,869,917 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w012w114w215w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb50c4d94…ee37
0xd32edf…ff58
11 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac3e4969…39e9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x3293a887…4401
0x1b6862…e19c
4 touches
1 conflict
0x294a17be…8e89
0x34b655…2a6f
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
15 conflicts on slot 0xb50c4d9487…5fee37
Audit this contract →
← previous block·next block →recent activity