← previous blocknext block →recent activity
Analyzing
Block #80,630,313
31 transactions · 23 stateful · 2026-06-11 18:11:37 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,630,313 · 31 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
1w02w13w25w36w07w114w015w123w424w028w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a10916…8ad0
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
8 touches
6 conflicts
0xdb067026…9eb8
0x69df8a…6292
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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 0xe5a1091603…158ad0
Audit this contract →
← previous block·next block →recent activity