← previous blocknext block →recent activity
Analyzing
Block #83,616,447
33 transactions · 24 stateful · 2026-06-25 14:15:45 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,616,447 · 33 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
3w04w17w010w015w016w117w218w119w221w322w123w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87c51bef…2368
0xd32edf…ff58
7 touches
6 conflicts
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xfd4e2262…cd8c
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x1c92ed9e…0324
0x34b655…2a6f
4 touches
1 conflict
0x21ca661f…6b6a
0x34b655…2a6f
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 0x87c51bef1f…0b2368
Audit this contract →
← previous block·next block →recent activity