← previous blocknext block →recent activity
Analyzing
Block #91,190,734
37 transactions · 30 stateful · 2026-07-28 23:37:28 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,190,734 · 37 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
5w06w07w19w111w212w013w114w219w022w125w326w427w229w332w133w034w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafc1bc62…f16b
0xd32edf…ff58
9 touches
10 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x6ea8fa8d…3dd6
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
10 conflicts on slot 0xafc1bc627e…edf16b
Audit this contract →
← previous block·next block →recent activity