← previous blocknext block →recent activity
Analyzing
Block #94,811,265
25 transactions · 18 stateful · 2026-08-10 15:29:40 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,811,265 · 25 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
1w03w14w26w37w48w512w614w415w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x384fdc6b…96a3
0xd32edf…ff58
15 touches
28 conflicts
0xe90b7bce…c2e0
0xfa32f9…f3f0
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
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 0x384fdc6bf7…e096a3
Audit this contract →
← previous block·next block →recent activity