← previous blocknext block →recent activity
Analyzing
Block #83,574,685
10 transactions · 10 stateful · 2026-06-25 09:37:02 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,574,685 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
6 touches
3 conflicts
0xbaff104b…3edb
0xa6afd3…d132
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x46c4691f…b730
0xa6afd3…d132
3 touches
1 conflict
0xb93e1f80…120c
0xa6afd3…d132
3 touches
1 conflict
0xb32929f5…83a9
0x34b655…2a6f
2 touches
0 conflicts
0xb72f4795…07ac
0x34b655…2a6f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity