← previous blocknext block →recent activity
Analyzing
Block #76,462,447
22 transactions · 16 stateful · 2026-05-23 10:49:47 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,462,447 · 22 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
2w04w18w09w111w214w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f7e3b7…e015
0x188d58…ea8e
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
6 touches
3 conflicts
0x3c599619…1286
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0xbad186…74ab
4 touches
1 conflict
0x8edd456e…c7e3
0x0555e3…2b9c
4 touches
1 conflict
0x9e25d1f0…0153
0xee8c0e…1242
4 touches
1 conflict
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
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: Uniswap: PoolManager
3 conflicts on slot 0x00f7e3b74f…eee015
Audit this contract →
← previous block·next block →recent activity