← previous blocknext block →recent activity
Analyzing
Block #96,591,509
21 transactions · 18 stateful · 2026-08-16 21:00:10 UTC
Parallelism
62/100
Blocked
44%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,591,509 · 21 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
0x6ee71872…73c8
0xd32edf…ff58
15 touches
28 conflicts
0x247e8081…9fb5
0x34b655…2a6f
4 touches
1 conflict
0x3e3f27ce…580c
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0xb1632c2f…d991
0x0a3323…0a3c
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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 0x6ee71872e3…c573c8
Audit this contract →
← previous block·next block →recent activity