← previous blocknext block →recent activity
Analyzing
Block #86,289,444
15 transactions · 12 stateful · 2026-07-07 23:16:49 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,289,444 · 15 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
1w03w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc02be3a4…dff6
0x188d58…ea8e
4 touches
1 conflict
0xc02be3a4…dff8
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa307c334…c9ae
0x754704…b603
4 touches
1 conflict
0xd821cffd…3ff0
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x86dbf0…eb2d
4 touches
1 conflict
0x56a919c4…ab49
0xad96c3…8d7c
4 touches
1 conflict
0x61d65579…ee3c
0xad96c3…8d7c
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 0xc02be3a4b1…9adff6
Audit this contract →
← previous block·next block →recent activity