← previous blocknext block →recent activity
Analyzing
Block #74,789,335
10 transactions · 7 stateful · 2026-05-15 16:41:17 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,789,335 · 10 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
1w02w13w24w05w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x6b319071…a105
0xc8689a…ee79
4 touches
1 conflict
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…000b
0x5d823e…89c6
4 touches
1 conflict
0x0175b7a6…1dba
0x5d823e…89c6
4 touches
1 conflict
0x0ef1e663…8f2a
0x5d823e…89c6
4 touches
1 conflict
0x78a99acb…07a1
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