← previous blocknext block →recent activity
Analyzing
Block #103,050,469
25 transactions · 23 stateful · 2026-09-08 13:24:06 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #103,050,469 · 25 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
1w02w13w24w35w46w18w415w516w517w018w124w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c1fde16…090c
0xd32edf…ff58
11 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x60166f33…683e
0x065c9d…c394
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0xfc7a2d65…2f58
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
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
15 conflicts on slot 0x6c1fde167a…ef090c
Audit this contract →
← previous block·next block →recent activity