← previous blocknext block →recent activity
Analyzing
Block #100,062,437
18 transactions · 17 stateful · 2026-08-29 02:14:40 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,062,437 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w414w015w416w517w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3554fc1…54dd
0xd32edf…ff58
9 touches
10 conflicts
0xa6b48d6e…0705
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x65bd5770…5ece
0x1b6862…e19c
4 touches
1 conflict
0x00f6a8a7…0e6e
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
0x34b655…2a6f
4 touches
1 conflict
0xbac9b836…66ad
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xb3554fc1a7…4454dd
Audit this contract →
← previous block·next block →recent activity