← previous blocknext block →recent activity
Analyzing
Block #100,591,111
20 transactions · 19 stateful · 2026-08-30 22:38:58 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,591,111 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w38w39w410w211w013w414w515w116w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc29d44fd…84ce
0xd32edf…ff58
9 touches
10 conflicts
0x90d24713…b88e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5165263d…ae1e
0x34b655…2a6f
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 0xc29d44fd02…2b84ce
Audit this contract →
← previous block·next block →recent activity