← previous blocknext block →recent activity
Analyzing
Block #84,575,259
16 transactions · 15 stateful · 2026-06-30 00:48:03 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,575,259 · 16 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
1w02w14w26w07w18w110w311w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0b900af…e3d8
0xd32edf…ff58
5 touches
3 conflicts
0xd996735f…8734
0x1b6862…e19c
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x29686688…0598
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
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
3 conflicts on slot 0xb0b900af06…52e3d8
Audit this contract →
← previous block·next block →recent activity