← previous blocknext block →recent activity
Analyzing
Block #100,029,093
23 transactions · 22 stateful · 2026-08-28 23:26:50 UTC
Parallelism
61/100
Blocked
73%
Avg conflicts / tx
2.35
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,029,093 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w47w58w59w613w614w715w816w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd793c2c…a312
0xd32edf…ff58
17 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 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…001b
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
36 conflicts on slot 0xcd793c2c89…b3a312
Audit this contract →
← previous block·next block →recent activity