← previous blocknext block →recent activity
Analyzing
Block #96,639,945
23 transactions · 21 stateful · 2026-08-17 01:03:46 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,639,945 · 23 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
1w02w13w24w35w48w19w010w011w112w013w115w219w020w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x324db0cd…8ad3
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xc2aacf41…5504
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0x324db0cd91…4c8ad3
Audit this contract →
← previous block·next block →recent activity