← previous blocknext block →recent activity
Analyzing
Block #101,016,873
37 transactions · 27 stateful · 2026-09-01 10:21:09 UTC
Parallelism
89/100
Blocked
37%
Avg conflicts / tx
0.51
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,016,873 · 37 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w29w110w213w116w017w123w027w129w330w235w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4953f83…f54d
0xd32edf…ff58
7 touches
6 conflicts
0x451e482b…7e7d
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
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
6 conflicts on slot 0xb4953f83c3…4af54d
Audit this contract →
← previous block·next block →recent activity