← previous blocknext block →recent activity
Analyzing
Block #101,066,220
27 transactions · 24 stateful · 2026-09-01 14:29:30 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,066,220 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w416w517w618w722w125w826w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2506bb…b472
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x93afca4c…b478
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
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
45 conflicts on slot 0xfe2506bbf7…d8b472
Audit this contract →
← previous block·next block →recent activity