← previous blocknext block →recent activity
Analyzing
Block #91,765,419
32 transactions · 23 stateful · 2026-07-30 23:50:49 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,765,419 · 32 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
2w03w14w25w36w49w010w115w016w019w120w021w122w229w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69dbfddb…51e6
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x07d110f6…e379
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
10 conflicts on slot 0x69dbfddb24…3451e6
Audit this contract →
← previous block·next block →recent activity