← previous blocknext block →recent activity
Analyzing
Block #84,064,541
17 transactions · 16 stateful · 2026-06-27 16:04:06 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,064,541 · 17 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
0x763dd151…d9de
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x117f1699…b264
0xa6afd3…d132
4 touches
1 conflict
0xd5d09c38…433a
0xa6afd3…d132
3 touches
1 conflict
0x588d2fec…5123
0xa6afd3…d132
3 touches
1 conflict
0x489bff18…82f3
0x34b655…2a6f
2 touches
0 conflicts
0x62d6e82b…a750
0x34b655…2a6f
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
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 0x763dd151da…97d9de
Audit this contract →
← previous block·next block →recent activity