← previous blocknext block →recent activity
Analyzing
Block #108,508,896
19 transactions · 18 stateful · 2026-09-27 16:08:05 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,508,896 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w110w012w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b0e9d54…2ad2
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xda6b535e…6d6c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xca841faa…486a
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
21 conflicts on slot 0x5b0e9d543d…8b2ad2
Audit this contract →
← previous block·next block →recent activity