← previous blocknext block →recent activity
Analyzing
Block #84,248,931
27 transactions · 21 stateful · 2026-06-28 12:32:13 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
1.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,248,931 · 27 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
1w02w13w24w35w46w57w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c37b45c…5920
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c6
0x1b6862…e19c
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 0x4c37b45c0f…255920
Audit this contract →
← previous block·next block →recent activity