← previous blocknext block →recent activity
Analyzing
Block #84,454,210
17 transactions · 11 stateful · 2026-06-29 11:20:10 UTC
Parallelism
65/100
Blocked
64%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,454,210 · 17 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
1w02w13w24w35w47w410w011w113w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f06f820…3fbd
0xd32edf…ff58
9 touches
10 conflicts
0xd821cffd…3ff0
0x754704…b603
8 touches
6 conflicts
0x61d65579…ee3c
0xad96c3…8d7c
8 touches
6 conflicts
0x00000000…0008
0x86dbf0…eb2d
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xed863ec8…90d9
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
10 conflicts on slot 0x4f06f82024…ed3fbd
Audit this contract →
← previous block·next block →recent activity