← previous blocknext block →recent activity
Analyzing
Block #102,052,018
24 transactions · 20 stateful · 2026-09-05 01:15:26 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,052,018 · 24 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
1w02w13w26w37w09w110w216w317w418w020w121w222w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbd9a866…e2ef
0xd32edf…ff58
9 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb4
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x4d7aaa4f…a8ec
0x34b655…2a6f
4 touches
1 conflict
0xcc8b6d32…6601
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
10 conflicts on slot 0xcbd9a8669c…4be2ef
Audit this contract →
← previous block·next block →recent activity