← previous blocknext block →recent activity
Analyzing
Block #108,653,913
24 transactions · 19 stateful · 2026-09-28 04:18:23 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,653,913 · 24 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
1w02w03w14w27w08w19w110w112w313w114w216w317w419w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7073bfef…0c98
0xd32edf…ff58
7 touches
6 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
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 0x7073bfeff6…470c98
Audit this contract →
← previous block·next block →recent activity