← previous blocknext block →recent activity
Analyzing
Block #84,060,452
24 transactions · 22 stateful · 2026-06-27 15:36:57 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,060,452 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w313w214w015w316w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xbf4d6c04…4fac
0xd32edf…ff58
5 touches
3 conflicts
0xc44e7516…5ee3
0xa6afd3…d132
4 touches
2 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd6071d1d…496a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xef65bff3…7c9d
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: Kuru Exchange: Market-WETH/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity