← previous blocknext block →recent activity
Analyzing
Block #84,457,122
29 transactions · 26 stateful · 2026-06-29 11:39:35 UTC
Parallelism
72/100
Blocked
46%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,457,122 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w08w114w015w116w217w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x56785e37…a197
0x065c9d…c394
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xe75cebb6…6b36
0x065c9d…c394
8 touches
6 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
6 touches
3 conflicts
0xc05b880b…7746
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 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-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity