← previous blocknext block →recent activity
Analyzing
Block #96,708,344
20 transactions · 18 stateful · 2026-08-17 06:47:47 UTC
Parallelism
55/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #96,708,344 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w610w711w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1af2bde7…b59b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xe01158fd…f97d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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 0x1af2bde7b7…afb59b
Audit this contract →
← previous block·next block →recent activity