← previous blocknext block →recent activity
Analyzing
Block #104,192,163
25 transactions · 16 stateful · 2026-09-12 13:31:33 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,192,163 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w38w09w113w014w120w021w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd76e94ce…51f2
0xd32edf…ff58
7 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x75ecc441…9de3
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x6aa624fd…a851
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
6 conflicts on slot 0xd76e94ce4f…d451f2
Audit this contract →
← previous block·next block →recent activity