← previous blocknext block →recent activity
Analyzing
Block #92,346,784
19 transactions · 16 stateful · 2026-08-02 00:35:00 UTC
Parallelism
58/100
Blocked
56%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,346,784 · 19 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
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fd6c06e…f0c3
0xd32edf…ff58
15 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x56153262…21ce
0x34b655…2a6f
6 touches
3 conflicts
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 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 0x4fd6c06e0c…fdf0c3
Audit this contract →
← previous block·next block →recent activity