← previous blocknext block →recent activity
Analyzing
Block #84,457,138
22 transactions · 19 stateful · 2026-06-29 11:39:41 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,457,138 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8dd1f0e…56a4
0xd32edf…ff58
15 touches
28 conflicts
0xd7c2ac74…4b65
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
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
28 conflicts on slot 0xf8dd1f0e4a…b756a4
Audit this contract →
← previous block·next block →recent activity