← previous blocknext block →recent activity
Analyzing
Block #101,502,733
14 transactions · 12 stateful · 2026-09-03 03:06:00 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,502,733 · 14 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
1w02w13w24w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f7f99a3…cbbd
0xd32edf…ff58
7 touches
6 conflicts
0x21163f51…05d4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x9bf56401…08f2
0x34b655…2a6f
4 touches
1 conflict
0xf5dddd0f…c9c7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21bf
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 0x6f7f99a3eb…04cbbd
Audit this contract →
← previous block·next block →recent activity