← previous blocknext block →recent activity
Analyzing
Block #84,359,268
17 transactions · 12 stateful · 2026-06-29 00:47:27 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,359,268 · 17 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
3w05w06w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7263b4fb…09dc
0xa6afd3…d132
4 touches
1 conflict
0xbfb25537…81da
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0xe99ebc4d…22f9
0x34b655…2a6f
4 touches
1 conflict
0xf1c6c001…65fc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
1 conflict on slot 0x7263b4fb47…e309dc
Audit this contract →
← previous block·next block →recent activity