← previous blocknext block →recent activity
Analyzing
Block #83,636,574
20 transactions · 16 stateful · 2026-06-25 16:30:17 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,636,574 · 20 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
3w05w07w08w110w113w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f1ff310…b809
0xd32edf…ff58
5 touches
3 conflicts
0x785889c9…0603
0x34b655…2a6f
4 touches
1 conflict
0x6290cbed…b15f
0x34b655…2a6f
4 touches
1 conflict
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0xf75859c9…cfab
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
3 conflicts on slot 0x5f1ff310d3…62b809
Audit this contract →
← previous block·next block →recent activity