← previous blocknext block →recent activity
Analyzing
Block #94,198,181
32 transactions · 24 stateful · 2026-08-08 11:51:53 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,198,181 · 32 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
1w03w14w27w38w49w514w415w616w726w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d3001e6…8792
0xd32edf…ff58
15 touches
28 conflicts
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0xc2aacf41…5503
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 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 0x4d3001e69e…d38792
Audit this contract →
← previous block·next block →recent activity