← previous blocknext block →recent activity
Analyzing
Block #103,050,530
17 transactions · 16 stateful · 2026-09-08 13:24:24 UTC
Parallelism
65/100
Blocked
38%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #103,050,530 · 17 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
1w02w13w26w28w39w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x536f6dba…03f2
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x1da7723c…80ae
0x1b6862…e19c
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x48ed1159…abe9
0x34ae4d…3fc5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0x536f6dba6f…8f03f2
Audit this contract →
← previous block·next block →recent activity