← previous blocknext block →recent activity
Analyzing
Block #100,633,005
35 transactions · 22 stateful · 2026-08-31 02:09:43 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,633,005 · 35 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
2w03w110w214w315w421w523w525w626w327w428w529w631w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6850dfd…0b6b
0xd32edf…ff58
13 touches
21 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x892daf6e…48d8
0x065c9d…c394
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x44a4bdef…c14d
0x065c9d…c394
5 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
21 conflicts on slot 0xa6850dfdab…900b6b
Audit this contract →
← previous block·next block →recent activity