← previous blocknext block →recent activity
Analyzing
Block #93,372,548
23 transactions · 20 stateful · 2026-08-05 14:36:49 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,372,548 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w09w110w211w012w113w214w318w419w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4887cb01…a5f1
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0x91855e…ac7e
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x830c3f44…44d3
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0012
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
6 conflicts on slot 0x4887cb013f…48a5f1
Audit this contract →
← previous block·next block →recent activity