← previous blocknext block →recent activity
Analyzing
Block #84,317,176
10 transactions · 8 stateful · 2026-06-28 20:06:48 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,317,176 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3287e4ec…eaa3
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0cfb5d79…7ccb
0xb754ba…508d
2 touches
0 conflicts
0x0cfb5d79…7ccc
0xb754ba…508d
2 touches
0 conflicts
0x12117fd0…ec1a
0xb754ba…508d
2 touches
0 conflicts
0x12117fd0…ec1b
0xb754ba…508d
2 touches
0 conflicts
0x1232a81d…88d7
0xb754ba…508d
2 touches
0 conflicts
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x3287e4ecfd…5aeaa3
Audit this contract →
← previous block·next block →recent activity