← previous blocknext block →recent activity
Analyzing
Block #96,131,880
24 transactions · 20 stateful · 2026-08-15 06:28:06 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,131,880 · 24 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
1w02w13w24w35w46w512w113w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5311ef64…af32
0xd32edf…ff58
15 touches
28 conflicts
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
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
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 0x5311ef64bf…d6af32
Audit this contract →
← previous block·next block →recent activity