← previous blocknext block →recent activity
Analyzing
Block #82,706,017
20 transactions · 17 stateful · 2026-06-21 08:53:10 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #82,706,017 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w27w38w49w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xf9f48af5…4205
0xa6afd3…d132
10 touches
10 conflicts
0x26470289…bb21
0xa6afd3…d132
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0xb05cd4f5…73d0
0x69df8a…6292
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity