← previous blocknext block →recent activity
Analyzing
Block #84,034,729
15 transactions · 12 stateful · 2026-06-27 12:45:27 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,034,729 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w06w17w29w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d5c395b…6b5a
0xa6afd3…d132
6 touches
3 conflicts
0x90a9e3f8…17ab
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
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…001b
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: Kuru Exchange: Market-WETH/USDC
3 conflicts on slot 0x2d5c395b26…9d6b5a
Audit this contract →
← previous block·next block →recent activity