← previous blocknext block →recent activity
Analyzing
Block #100,110,357
19 transactions · 17 stateful · 2026-08-29 06:15:56 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,110,357 · 19 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
1w02w13w24w36w412w413w514w015w616w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51329414…4c5b
0xd32edf…ff58
13 touches
21 conflicts
0x5896e8c1…dde5
0x34b655…2a6f
6 touches
3 conflicts
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
0x6d43ee99…bdd8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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 0x5132941479…ff4c5b
Audit this contract →
← previous block·next block →recent activity