← previous blocknext block →recent activity
Analyzing
Block #101,093,129
35 transactions · 26 stateful · 2026-09-01 16:45:08 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,093,129 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w29w011w012w315w116w126w228w329w030w431w032w133w134w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf766373f…828f
0xd32edf…ff58
7 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0xb19fad4f…18d0
0x065c9d…c394
5 touches
3 conflicts
0x6dedaff6…161b
0x34b655…2a6f
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
6 conflicts on slot 0xf766373f1b…7c828f
Audit this contract →
← previous block·next block →recent activity