← previous blocknext block →recent activity
Analyzing
Block #91,111,264
28 transactions · 27 stateful · 2026-07-28 16:57:42 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,111,264 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w58w19w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93d0be92…949a
0xd32edf…ff58
15 touches
28 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xcc58c80b…ff79
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
28 conflicts on slot 0x93d0be9217…63949a
Audit this contract →
← previous block·next block →recent activity