← previous blocknext block →recent activity
Analyzing
Block #91,810,165
16 transactions · 13 stateful · 2026-07-31 03:35:55 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,810,165 · 16 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
1w02w13w26w37w09w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ed1e213…dd38
0xd32edf…ff58
7 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x56a284d9…32e4
0x34b655…2a6f
4 touches
1 conflict
0x6f8644f7…10fa
0x34b655…2a6f
4 touches
1 conflict
0x90fb38c3…964c
0x34b655…2a6f
4 touches
1 conflict
0xbb8dc535…4fe7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
6 conflicts on slot 0x9ed1e21396…d3dd38
Audit this contract →
← previous block·next block →recent activity