← previous blocknext block →recent activity
Analyzing
Block #87,638,557
23 transactions · 18 stateful · 2026-07-14 05:38:21 UTC
Parallelism
91/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,638,557 · 23 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
1w03w04w15w16w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x703b861a…cbe4
0x188d58…ea8e
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf7640726…19a2
0x2a68ba…90c5
4 touches
1 conflict
0x4855732e…993f
0x699abc…6a3b
4 touches
1 conflict
0x63d0e385…8873
0x699abc…6a3b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0b1cc6d1…1f59
0x851145…3f07
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
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
1 conflict on slot 0x703b861af3…7acbe4
Audit this contract →
← previous block·next block →recent activity