← previous blocknext block →recent activity
Analyzing
Block #96,568,870
29 transactions · 24 stateful · 2026-08-16 19:06:17 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,568,870 · 29 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
1w02w13w24w311w413w014w115w216w317w420w023w024w126w127w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e060ea2…d5d3
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x103de0…bb55
8 touches
6 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
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 0x2e060ea247…37d5d3
Audit this contract →
← previous block·next block →recent activity