← previous blocknext block →recent activity
Analyzing
Block #83,875,599
14 transactions · 13 stateful · 2026-06-26 19:05:07 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,875,599 · 14 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
1w02w13w25w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc05b880b…7746
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x330f3d99…5e3c
0x40c49f…2af0
2 touches
0 conflicts
0x3e8338b3…61ac
0x40c49f…2af0
2 touches
0 conflicts
0xb98f9147…2139
0x40c49f…2af0
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity