← previous blocknext block →recent activity
Analyzing
Block #96,561,672
18 transactions · 13 stateful · 2026-08-16 18:30:05 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,561,672 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w110w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fe666c3…085e
0xd32edf…ff58
11 touches
15 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
4 touches
1 conflict
0x63f5c02f…6853
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x850662…52d0
4 touches
1 conflict
0x00000000…0002
0x850662…52d0
4 touches
1 conflict
0x00000000…0004
0x850662…52d0
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001e
0x1b6862…e19c
2 touches
0 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
15 conflicts on slot 0x5fe666c350…2b085e
Audit this contract →
← previous block·next block →recent activity