← previous blocknext block →recent activity
Analyzing
Block #101,966,523
25 transactions · 19 stateful · 2026-09-04 18:02:09 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,966,523 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w211w312w013w115w317w218w421w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb091446c…59f6
0xd32edf…ff58
7 touches
6 conflicts
0x91b13e91…855d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x1045386d…cb88
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
6 conflicts on slot 0xb091446c9a…4559f6
Audit this contract →
← previous block·next block →recent activity