← previous blocknext block →recent activity
Analyzing
Block #100,132,503
22 transactions · 22 stateful · 2026-08-29 08:07:26 UTC
Parallelism
68/100
Blocked
64%
Avg conflicts / tx
1.55
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,132,503 · 22 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
1w02w13w24w35w47w18w29w210w414w515w617w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x947f551c…14b5
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x91220b8f…7a06
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
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
21 conflicts on slot 0x947f551ce2…d314b5
Audit this contract →
← previous block·next block →recent activity