← previous blocknext block →recent activity
Analyzing
Block #82,437,989
14 transactions · 12 stateful · 2026-06-20 03:01:46 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,437,989 · 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
1w02w13w14w05w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66c5e348…51d0
0xa6afd3…d132
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb24496eb…c6ff
0xa6afd3…d132
3 touches
1 conflict
0xd9f5ade4…58a2
0x065c9d…c394
3 touches
1 conflict
0x6a3e6a40…e460
0x0594c7…a3be
2 touches
0 conflicts
0xa1e29623…337a
0x3bd359…433a
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 0x66c5e3484c…3451d0
Audit this contract →
← previous block·next block →recent activity