← previous blocknext block →recent activity
Analyzing
Block #106,198,572
25 transactions · 24 stateful · 2026-09-19 14:16:23 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,198,572 · 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
1w02w13w24w35w46w07w010w011w116w118w119w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7169c542…4a14
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 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
0x1f8a126c…9aa7
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
10 conflicts on slot 0x7169c542e7…d84a14
Audit this contract →
← previous block·next block →recent activity