← previous blocknext block →recent activity
Analyzing
Block #96,151,103
19 transactions · 13 stateful · 2026-08-15 08:04:49 UTC
Parallelism
68/100
Blocked
62%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,151,103 · 19 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
1w02w13w24w35w48w111w114w016w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc545b9da…d309
0xd32edf…ff58
11 touches
15 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xa060b594…669d
0x754704…b603
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x00000000…0003
0x834d94…8555
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
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 0xc545b9daa5…05d309
Audit this contract →
← previous block·next block →recent activity