← previous blocknext block →recent activity
Analyzing
Block #100,619,321
23 transactions · 22 stateful · 2026-08-31 01:00:53 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,619,321 · 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
1w02w13w24w36w07w08w19w010w112w215w416w517w619w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59f3cdc4…e604
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xedbdafc3…1492
0x34b655…2a6f
8 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0x59f3cdc4ff…02e604
Audit this contract →
← previous block·next block →recent activity