← previous blocknext block →recent activity
Analyzing
Block #100,810,286
33 transactions · 26 stateful · 2026-08-31 17:01:42 UTC
Parallelism
82/100
Blocked
69%
Avg conflicts / tx
1.27
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,810,286 · 33 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
1w02w13w24w35w46w07w18w210w511w112w214w521w332w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb1f9279…5d53
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0xf5b5f7…6d70
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x93afca4c…b47b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
15 conflicts on slot 0xfb1f927952…6b5d53
Audit this contract →
← previous block·next block →recent activity