← previous blocknext block →recent activity
Analyzing
Block #80,101,870
34 transactions · 30 stateful · 2026-06-09 07:28:07 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
2.24
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #80,101,870 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w29w310w411w512w613w726w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0xe5a10916…8ad0
0xa6afd3…d132
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x40970e69…da50
0x69df8a…6292
16 touches
28 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
16 touches
28 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
16 touches
28 conflicts
0xdb067026…9eb8
0x69df8a…6292
16 touches
28 conflicts
0xfd72a574…e07a
0xa6afd3…d132
16 touches
28 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
36 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity