← previous blocknext block →recent activity
Analyzing
Block #100,849,294
23 transactions · 20 stateful · 2026-08-31 20:18:08 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,849,294 · 23 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
1w02w13w24w35w06w315w416w519w422w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e4b01f8…5d3d
0xd32edf…ff58
7 touches
6 conflicts
0x14d1bf0e…e09c
0x1b6862…e19c
6 touches
3 conflicts
0x6518075e…2b17
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x7d554c3a…eedb
0x40c49f…2af0
5 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
6 conflicts on slot 0x5e4b01f8df…b65d3d
Audit this contract →
← previous block·next block →recent activity