← previous blocknext block →recent activity
Analyzing
Block #84,039,132
19 transactions · 16 stateful · 2026-06-27 13:14:50 UTC
Parallelism
89/100
Blocked
31%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,039,132 · 19 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
1w02w13w17w110w012w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a996
0x188d58…ea8e
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0xa6885dd0…9371
0x065c9d…c394
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x2d8243b9…337b
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf0
0x34b655…2a6f
4 touches
1 conflict
0xb99958f6…ccf1
0x34b655…2a6f
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 0x4dd1db394e…28a994
Audit this contract →
← previous block·next block →recent activity