← previous blocknext block →recent activity
Analyzing
Block #73,675,921
18 transactions · 16 stateful · 2026-05-10 12:46:04 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,675,921 · 18 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
1w02w13w04w05w16w27w211w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0x13a52d2d…c0fe
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x3e733ae4…4598
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 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity