← previous blocknext block →recent activity
Analyzing
Block #93,267,178
31 transactions · 27 stateful · 2026-08-05 05:47:02 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,267,178 · 31 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
1w02w13w24w35w49w510w611w713w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0dc3e22…4f1d
0xd32edf…ff58
15 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
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 0xc0dc3e2243…9e4f1d
Audit this contract →
← previous block·next block →recent activity