← previous blocknext block →recent activity
Analyzing
Block #83,861,965
21 transactions · 18 stateful · 2026-06-26 17:34:07 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,861,965 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w110w111w112w213w314w315w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3de5fb8b…400a
0xa6afd3…d132
8 touches
6 conflicts
0x0b16149e…7d4d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x4895691e…2cd2
0x065c9d…c394
4 touches
2 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea4b86ec…900f
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
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
6 conflicts on slot 0x3de5fb8b37…25400a
Audit this contract →
← previous block·next block →recent activity