← previous blocknext block →recent activity
Analyzing
Block #93,174,439
35 transactions · 30 stateful · 2026-08-04 22:00:46 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,174,439 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w513w014w121w124w627w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe209dc61…24d7
0xd32edf…ff58
13 touches
21 conflicts
0x8eef368f…aa21
0x34b655…2a6f
8 touches
6 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc26566fc…66a8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xfac61869…a55d
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
21 conflicts on slot 0xe209dc61f5…3624d7
Audit this contract →
← previous block·next block →recent activity