← previous blocknext block →recent activity
Analyzing
Block #100,920,289
24 transactions · 23 stateful · 2026-09-01 02:15:14 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,920,289 · 24 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
1w02w13w24w05w06w17w28w09w111w213w315w316w420w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1acae764…9845
0xd32edf…ff58
9 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xf55e6412…f1fa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x1045386d…cb8b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
10 conflicts on slot 0x1acae76410…6c9845
Audit this contract →
← previous block·next block →recent activity