← previous blocknext block →recent activity
Analyzing
Block #86,796,239
27 transactions · 19 stateful · 2026-07-10 07:45:31 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,796,239 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w010w011w114w215w016w118w220w124w325w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8b6e4c2…e20a
0x188d58…ea8e
8 touches
6 conflicts
0xfc4fe1a9…a230
0xd32edf…ff58
7 touches
6 conflicts
0x0dbf9688…c6cf
0x43cf54…7777
6 touches
3 conflicts
0xe8b6e4c2…e20c
0x188d58…ea8e
6 touches
3 conflicts
0x6f845aff…9fc9
0x3bd359…433a
6 touches
3 conflicts
0xf901bf23…beaa
0x3bd359…433a
6 touches
3 conflicts
0x062b2598…4e28
0x43cf54…7777
6 touches
3 conflicts
0x2e99de81…c26b
0x43cf54…7777
6 touches
3 conflicts
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
6 conflicts on slot 0xe8b6e4c2d9…01e20a
Audit this contract →
← previous block·next block →recent activity