← previous blocknext block →recent activity
Analyzing
Block #93,499,311
24 transactions · 23 stateful · 2026-08-06 01:14:07 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,499,311 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w27w310w211w312w413w514w015w116w018w019w120w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3402044…f0ff
0xd32edf…ff58
11 touches
15 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
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…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
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
15 conflicts on slot 0xf3402044cf…23f0ff
Audit this contract →
← previous block·next block →recent activity