← previous blocknext block →recent activity
Analyzing
Block #101,065,632
20 transactions · 20 stateful · 2026-09-01 14:26:32 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,065,632 · 20 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
1w02w13w25w17w29w310w411w513w014w116w119w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05fb17a1…2794
0xd32edf…ff58
13 touches
21 conflicts
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x62b937eb…c75c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
21 conflicts on slot 0x05fb17a190…4c2794
Audit this contract →
← previous block·next block →recent activity