← previous blocknext block →recent activity
Analyzing
Block #108,377,392
21 transactions · 18 stateful · 2026-09-27 05:06:09 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,377,392 · 21 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
1w03w04w17w18w09w111w012w115w219w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bf5f8a2…0ecb
0xd32edf…ff58
7 touches
6 conflicts
0xe4560b78…00a8
0x065c9d…c394
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x49890ced…6f23
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 0x5bf5f8a2be…580ecb
Audit this contract →
← previous block·next block →recent activity