← previous blocknext block →recent activity
Analyzing
Block #100,853,452
19 transactions · 17 stateful · 2026-08-31 20:39:03 UTC
Parallelism
74/100
Blocked
71%
Avg conflicts / tx
1.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,853,452 · 19 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
1w02w13w25w16w17w09w310w111w212w213w314w415w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c7f0e19…f240
0xd32edf…ff58
9 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xae7f6f8f…b68a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x6d43ee99…bdd6
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
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 0x6c7f0e19bd…dbf240
Audit this contract →
← previous block·next block →recent activity