← previous blocknext block →recent activity
Analyzing
Block #100,878,993
28 transactions · 21 stateful · 2026-08-31 22:47:31 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,878,993 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w221w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x363bb105…6a6c
0xd32edf…ff58
15 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xcfa38496…c84f
0xee8c0e…1242
4 touches
1 conflict
0x00000000…0002
0x25ef1a…5bf1
4 touches
1 conflict
0x9654e93b…e153
0x34b655…2a6f
4 touches
1 conflict
0xae0fd6cf…f503
0x34b655…2a6f
4 touches
1 conflict
0xf2410d5d…8153
0x34b655…2a6f
4 touches
1 conflict
0x0f9a0bfe…d018
0x754704…b603
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
28 conflicts on slot 0x363bb105c8…366a6c
Audit this contract →
← previous block·next block →recent activity