← previous blocknext block →recent activity
Analyzing
Block #100,876,211
28 transactions · 25 stateful · 2026-08-31 22:33:32 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,876,211 · 28 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
1w02w13w24w35w46w59w016w317w418w520w321w626w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16852bb3…5ed6
0xd32edf…ff58
11 touches
15 conflicts
0x0778475b…bd75
0x2a68ba…90c5
10 touches
10 conflicts
0x4ffc0987…d319
0x065c9d…c394
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 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 0x16852bb36c…955ed6
Audit this contract →
← previous block·next block →recent activity