← previous blocknext block →recent activity
Analyzing
Block #100,031,313
33 transactions · 32 stateful · 2026-08-28 23:38:01 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
1.03
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,031,313 · 33 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
1w02w13w24w35w06w17w48w49w510w613w522w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c0ccd52…b714
0xd32edf…ff58
13 touches
21 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
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
21 conflicts on slot 0x5c0ccd52d9…58b714
Audit this contract →
← previous block·next block →recent activity