← previous blocknext block →recent activity
Analyzing
Block #84,039,778
12 transactions · 10 stateful · 2026-06-27 13:19:09 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,039,778 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x7c5260f4…bd96
0xa6afd3…d132
6 touches
3 conflicts
0xda52da6d…ff90
0xa6afd3…d132
4 touches
1 conflict
0x2d5c395b…6b5a
0xa6afd3…d132
4 touches
1 conflict
0x76dec3ef…ef55
0xa6afd3…d132
3 touches
1 conflict
0x0da35ee6…13aa
0xa6afd3…d132
3 touches
1 conflict
0xb7432e0e…7b85
0xa6afd3…d132
3 touches
1 conflict
0x01addec0…ca84
0xa6afd3…d132
3 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: Kuru Exchange: Market-WETH/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity