← previous blocknext block →recent activity
Analyzing
Block #91,247,374
24 transactions · 22 stateful · 2026-07-29 04:22:25 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,247,374 · 24 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
1w02w13w24w36w08w19w010w115w116w217w319w221w322w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e9e816c…637d
0xd32edf…ff58
7 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xd697e595…8cf3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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 0x4e9e816c2f…dd637d
Audit this contract →
← previous block·next block →recent activity