← previous blocknext block →recent activity
Analyzing
Block #83,410,983
25 transactions · 23 stateful · 2026-06-24 15:24:39 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,410,983 · 25 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
1w02w13w14w210w011w112w213w314w315w316w422w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95bf43ef…eb6f
0xd32edf…ff58
9 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd4c913d7…343f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
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 0x95bf43efee…a5eb6f
Audit this contract →
← previous block·next block →recent activity