← previous blocknext block →recent activity
Analyzing
Block #100,248,566
27 transactions · 25 stateful · 2026-08-29 17:52:31 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.26
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,248,566 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w18w213w515w116w624w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8006ffa8…7369
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…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x6d43ee99…bdda
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 0x8006ffa8b7…3a7369
Audit this contract →
← previous block·next block →recent activity