← previous blocknext block →recent activity
Analyzing
Block #100,094,668
35 transactions · 25 stateful · 2026-08-29 04:56:56 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,094,668 · 35 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
1w02w13w210w016w317w418w019w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x350ecd0d…f815
0xd32edf…ff58
9 touches
10 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
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…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd18a8dca…452d
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 0x350ecd0d1d…29f815
Audit this contract →
← previous block·next block →recent activity