← previous blocknext block →recent activity
Analyzing
Block #100,095,748
33 transactions · 25 stateful · 2026-08-29 05:02:23 UTC
Parallelism
76/100
Blocked
52%
Avg conflicts / tx
0.94
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,095,748 · 33 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w515w516w421w423w624w730w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3706803a…c174
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xba5743c7…21c3
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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…001c
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 0x3706803ac9…a7c174
Audit this contract →
← previous block·next block →recent activity