← previous blocknext block →recent activity
Analyzing
Block #92,335,351
25 transactions · 22 stateful · 2026-08-01 23:37:31 UTC
Parallelism
60/100
Blocked
59%
Avg conflicts / tx
1.4
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #92,335,351 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbaad6f2e…f3f3
0xd32edf…ff58
15 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
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 0xbaad6f2e55…49f3f3
Audit this contract →
← previous block·next block →recent activity