← previous blocknext block →recent activity
Analyzing
Block #96,608,040
31 transactions · 21 stateful · 2026-08-16 22:23:19 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,608,040 · 31 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
1w09w010w113w014w115w216w317w118w420w221w323w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60bd2560…c559
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0x103de0…bb55
10 touches
10 conflicts
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
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
15 conflicts on slot 0x60bd2560dc…8dc559
Audit this contract →
← previous block·next block →recent activity