← previous blocknext block →recent activity
Analyzing
Block #84,279,194
38 transactions · 21 stateful · 2026-06-28 15:53:48 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,279,194 · 38 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
1w02w13w24w35w46w07w18w211w012w127w028w130w031w032w135w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b68b5cf…b1e5
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xd53220ed…4734
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 0x3b68b5cfb5…f1b1e5
Audit this contract →
← previous block·next block →recent activity