← previous blocknext block →recent activity
Analyzing
Block #83,945,369
19 transactions · 16 stateful · 2026-06-27 02:50:09 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,945,369 · 19 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
1w02w13w26w18w39w010w111w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd3eef9c…d2fb
0xd32edf…ff58
7 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x90a9e3f8…17ab
0x34b655…2a6f
6 touches
3 conflicts
0x57567cd7…0a28
0x34b655…2a6f
4 touches
1 conflict
0x2c45e1a9…ddef
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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 0xcd3eef9c4c…b6d2fb
Audit this contract →
← previous block·next block →recent activity