← previous blocknext block →recent activity
Analyzing
Block #79,021,657
30 transactions · 21 stateful · 2026-06-04 07:10:00 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #79,021,657 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w111w012w113w214w315w416w217w321w222w525w026w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xa19aba84…8922
0xa6afd3…d132
8 touches
6 conflicts
0x46b62326…9b3c
0xa6afd3…d132
8 touches
6 conflicts
0xdb067026…9eb8
0x69df8a…6292
8 touches
6 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
8 touches
6 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
8 touches
6 conflicts
0xa02e5cdd…76b8
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity