← previous blocknext block →recent activity
Analyzing
Block #83,202,555
32 transactions · 23 stateful · 2026-06-23 16:12:14 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
1.09
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,202,555 · 32 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w613w814w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93e1d156…6e8c
0xd32edf…ff58
15 touches
28 conflicts
0x731e6d82…2883
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
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 0x93e1d1561c…836e8c
Audit this contract →
← previous block·next block →recent activity