← previous blocknext block →recent activity
Analyzing
Block #100,706,621
30 transactions · 24 stateful · 2026-08-31 08:20:01 UTC
Parallelism
77/100
Blocked
46%
Avg conflicts / tx
0.97
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,706,621 · 30 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
1w02w13w24w35w411w016w017w119w520w622w125w426w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35d77c27…dfd8
0xd32edf…ff58
13 touches
21 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
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…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
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
21 conflicts on slot 0x35d77c2700…56dfd8
Audit this contract →
← previous block·next block →recent activity