← previous blocknext block →recent activity
Analyzing
Block #84,363,569
26 transactions · 23 stateful · 2026-06-29 01:16:08 UTC
Parallelism
69/100
Blocked
48%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,363,569 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w413w514w615w718w419w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56e111b3…49ed
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xdb95e18e…c739
0x1b6862…e19c
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
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
28 conflicts on slot 0x56e111b303…6949ed
Audit this contract →
← previous block·next block →recent activity