← previous blocknext block →recent activity
Analyzing
Block #76,437,999
13 transactions · 10 stateful · 2026-05-23 08:07:08 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,437,999 · 13 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
1w02w05w08w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0x8b4f8b4a…6d9c
0x34b655…2a6f
4 touches
1 conflict
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x5bc4eff9…03ee
0x065c9d…c394
3 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
1 conflict on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity