← previous blocknext block →recent activity
Analyzing
Block #76,224,802
8 transactions · 7 stateful · 2026-05-22 08:27:37 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,224,802 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46cb45de…a567
0x188d58…ea8e
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0xd4d2a2e5…6be0
0x0555e3…2b9c
2 touches
0 conflicts
0xee0a9ebb…c425
0x0555e3…2b9c
2 touches
0 conflicts
0xab8cd3e2…c098
0x065c9d…c394
2 touches
0 conflicts
0x46cb45de…a569
0x188d58…ea8e
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: Uniswap: PoolManager
1 conflict on slot 0x46cb45de01…66a567
Audit this contract →
← previous block·next block →recent activity