← previous blocknext block →recent activity
Analyzing
Block #84,353,433
23 transactions · 21 stateful · 2026-06-29 00:08:30 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,353,433 · 23 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
1w02w13w24w36w07w38w09w112w013w115w016w117w118w119w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5afc3b93…602f
0xd32edf…ff58
7 touches
6 conflicts
0x75cdffd8…c217
0x34b655…2a6f
6 touches
3 conflicts
0xd6d4eb00…30f3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x78694995…f668
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 0x5afc3b9392…ea602f
Audit this contract →
← previous block·next block →recent activity