← previous blocknext block →recent activity
Analyzing
Block #96,283,469
19 transactions · 15 stateful · 2026-08-15 19:10:34 UTC
Parallelism
58/100
Blocked
47%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,283,469 · 19 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
1w02w13w24w35w46w57w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf563025…d0b8
0xd32edf…ff58
15 touches
28 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0001
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0009
0x04ddf6…7f33
2 touches
0 conflicts
0x0ef74796…cd18
0x0a3323…0a3c
2 touches
0 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
28 conflicts on slot 0xaf563025a0…72d0b8
Audit this contract →
← previous block·next block →recent activity