← previous blocknext block →recent activity
Analyzing
Block #100,917,731
20 transactions · 19 stateful · 2026-09-01 02:02:22 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,917,731 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w36w07w412w413w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc376379a…c017
0xd32edf…ff58
9 touches
10 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
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
10 conflicts on slot 0xc376379a24…f3c017
Audit this contract →
← previous block·next block →recent activity