← previous blocknext block →recent activity
Analyzing
Block #108,494,956
24 transactions · 19 stateful · 2026-09-27 14:57:54 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,494,956 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w211w212w313w414w015w316w118w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cc6ebc7…9105
0xd32edf…ff58
9 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x2a15be31…7662
0x065c9d…c394
6 touches
3 conflicts
0x0de7749d…5bef
0x34b655…2a6f
4 touches
1 conflict
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x00000000…001c
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
10 conflicts on slot 0x0cc6ebc708…5e9105
Audit this contract →
← previous block·next block →recent activity