← previous blocknext block →recent activity
Analyzing
Block #84,362,070
35 transactions · 32 stateful · 2026-06-29 01:06:09 UTC
Parallelism
89/100
Blocked
38%
Avg conflicts / tx
0.49
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,362,070 · 35 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
1w02w13w25w06w17w08w110w013w315w020w021w124w125w126w127w230w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x145e2aa8…2601
0xd32edf…ff58
7 touches
6 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x928d6b23…536f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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 0x145e2aa8e6…2e2601
Audit this contract →
← previous block·next block →recent activity