← previous blocknext block →recent activity
Analyzing
Block #100,137,920
16 transactions · 16 stateful · 2026-08-29 08:34:52 UTC
Parallelism
56/100
Blocked
69%
Avg conflicts / tx
1.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,137,920 · 16 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
1w02w13w24w35w46w27w210w511w613w414w515w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb390ad25…63db
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x1da7723c…80ac
0x1b6862…e19c
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
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 0xb390ad25a9…d063db
Audit this contract →
← previous block·next block →recent activity