← previous blocknext block →recent activity
Analyzing
Block #96,112,440
20 transactions · 17 stateful · 2026-08-15 04:50:17 UTC
Parallelism
50/100
Blocked
59%
Avg conflicts / tx
2.3
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,112,440 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w913w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x520c2c55…d954
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0xa060b594…669d
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x00000000…0003
0x834d94…8555
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0xd0e02ea0…f6f3
0x065c9d…c394
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
45 conflicts on slot 0x520c2c55a8…c1d954
Audit this contract →
← previous block·next block →recent activity