← previous blocknext block →recent activity
Analyzing
Block #108,309,877
26 transactions · 19 stateful · 2026-09-26 23:26:25 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,309,877 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w09w512w614w724w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44016757…c134
0xd32edf…ff58
9 touches
10 conflicts
0x91220b8f…7a02
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xd69b107a…debe
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
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 0x4401675720…dec134
Audit this contract →
← previous block·next block →recent activity