← previous blocknext block →recent activity
Analyzing
Block #94,751,264
33 transactions · 28 stateful · 2026-08-10 10:27:35 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,751,264 · 33 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
1w02w13w24w35w49w514w522w625w627w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0f6038b…8035
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
10 touches
10 conflicts
0x9256b810…52c8
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0xe0f6038bfd…5a8035
Audit this contract →
← previous block·next block →recent activity