← previous blocknext block →recent activity
Analyzing
Block #108,923,317
10 transactions · 8 stateful · 2026-09-29 02:57:48 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,923,317 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1af802e4…72e8
0xd32edf…ff58
5 touches
3 conflicts
0x2ce2d49e…d18a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0056
0x1b6862…e19c
4 touches
1 conflict
0x4b1a00ef…9007
0x1b6862…e19c
4 touches
1 conflict
0x615d7983…1e54
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
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
3 conflicts on slot 0x1af802e472…6172e8
Audit this contract →
← previous block·next block →recent activity