← previous blocknext block →recent activity
Analyzing
Block #91,130,381
18 transactions · 14 stateful · 2026-07-28 18:33:51 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,130,381 · 18 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
1w02w13w24w35w49w510w013w115w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64a8af69…c905
0xd32edf…ff58
11 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2c75ca93…a569
0x34b655…2a6f
6 touches
3 conflicts
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x54d68470…4b32
0x34b655…2a6f
4 touches
1 conflict
0x589623ea…8ce2
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 0x64a8af6981…d8c905
Audit this contract →
← previous block·next block →recent activity