← previous blocknext block →recent activity
Analyzing
Block #100,629,434
20 transactions · 17 stateful · 2026-08-31 01:51:45 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,629,434 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w07w08w111w213w315w116w217w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62ed68c6…d1cd
0xd32edf…ff58
7 touches
6 conflicts
0xa242e227…2e45
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x6c28863e…840e
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xa8bb84ae…51bc
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 0x62ed68c628…ebd1cd
Audit this contract →
← previous block·next block →recent activity