← previous blocknext block →recent activity
Analyzing
Block #96,307,431
27 transactions · 23 stateful · 2026-08-15 21:11:04 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
1.37
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,307,431 · 27 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
1w02w14w25w36w49w114w515w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6d204df…d4ff
0xd32edf…ff58
15 touches
28 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x9af63a6a…6821
0x34b655…2a6f
4 touches
1 conflict
0xbe327ece…a92e
0x065c9d…c394
4 touches
1 conflict
0xb4b03a70…7c86
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
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 0xa6d204dfcf…57d4ff
Audit this contract →
← previous block·next block →recent activity