← previous blocknext block →recent activity
Analyzing
Block #84,023,666
30 transactions · 21 stateful · 2026-06-27 11:31:49 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,023,666 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w09w119w020w121w224w025w128w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x144e8064…31fd
0xd32edf…ff58
11 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x99246de6…5bd5
0x34b655…2a6f
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
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
15 conflicts on slot 0x144e806400…f131fd
Audit this contract →
← previous block·next block →recent activity