← previous blocknext block →recent activity
Analyzing
Block #100,613,713
24 transactions · 22 stateful · 2026-08-31 00:32:41 UTC
Parallelism
75/100
Blocked
68%
Avg conflicts / tx
1.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,613,713 · 24 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
1w02w13w24w35w48w39w410w515w517w418w521w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98b4e7f5…90cb
0xd32edf…ff58
11 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 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…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c6
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 0x98b4e7f522…5e90cb
Audit this contract →
← previous block·next block →recent activity