← previous blocknext block →recent activity
Analyzing
Block #96,388,447
24 transactions · 19 stateful · 2026-08-16 03:58:33 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,388,447 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w19w010w111w012w113w014w016w217w118w320w021w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f0f5b28…45ae
0xd32edf…ff58
5 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x6e6ab4cf…7074
0x065c9d…c394
4 touches
1 conflict
0x427dec7f…61c6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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
3 conflicts on slot 0x5f0f5b28a1…e545ae
Audit this contract →
← previous block·next block →recent activity