← previous blocknext block →recent activity
Analyzing
Block #94,279,771
36 transactions · 32 stateful · 2026-08-08 18:45:26 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,279,771 · 36 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
1w02w13w24w35w47w19w115w519w624w727w128w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d52e5ff…63ce
0xd32edf…ff58
15 touches
28 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
8 touches
6 conflicts
0x00000000…0001
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0003
0x0d73bf…be07
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
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 0x0d52e5ff74…8d63ce
Audit this contract →
← previous block·next block →recent activity