← previous blocknext block →recent activity
Analyzing
Block #94,739,984
20 transactions · 17 stateful · 2026-08-10 09:30:07 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,739,984 · 20 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
1w02w13w24w37w18w49w011w112w114w215w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f48fa32…e367
0xd32edf…ff58
9 touches
10 conflicts
0xbedeb464…b381
0x34b655…2a6f
6 touches
3 conflicts
0xe8d58d34…426d
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x21d8e673…067a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
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
10 conflicts on slot 0x5f48fa32c7…52e367
Audit this contract →
← previous block·next block →recent activity