← previous blocknext block →recent activity
Analyzing
Block #85,145,803
16 transactions · 12 stateful · 2026-07-02 16:13:36 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,145,803 · 16 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
1w02w03w05w19w110w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a1e6958…6dc5
0x188d58…ea8e
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3a1e6958…6dc3
0x188d58…ea8e
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x56a919c4…ab49
0xad96c3…8d7c
4 touches
1 conflict
0x08487f7f…fa85
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0005
0x2e37c3…e40f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 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
1 conflict on slot 0x3a1e695869…4c6dc5
Audit this contract →
← previous block·next block →recent activity