← previous blocknext block →recent activity
Analyzing
Block #101,306,193
23 transactions · 19 stateful · 2026-09-02 10:37:02 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,306,193 · 23 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
1w02w13w24w36w07w18w09w111w312w415w016w117w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e0bf2de…877f
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x6b1259e6…4e12
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
6 conflicts on slot 0x4e0bf2de33…35877f
Audit this contract →
← previous block·next block →recent activity