← previous blocknext block →recent activity
Analyzing
Block #92,443,186
20 transactions · 19 stateful · 2026-08-02 08:39:47 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,443,186 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w38w410w511w312w413w514w615w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcde22857…6ba6
0xd32edf…ff58
11 touches
15 conflicts
0xd00c8ec8…999f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x35801c67…bcc1
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0xcde228574b…2d6ba6
Audit this contract →
← previous block·next block →recent activity