← previous blocknext block →recent activity
Analyzing
Block #84,079,707
14 transactions · 10 stateful · 2026-06-27 17:45:04 UTC
Parallelism
86/100
Blocked
10%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,079,707 · 14 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
1w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb359b267…05dc
0xa6afd3…d132
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xb3eae1cb…7249
0x1111b3…4111
2 touches
0 conflicts
0x676931a1…029d
0x754704…b603
2 touches
0 conflicts
0xb5b71470…8bb8
0x754704…b603
2 touches
0 conflicts
0xe782fcdb…edef
0x754704…b603
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0xb359b26701…4205dc
Audit this contract →
← previous block·next block →recent activity