pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,629,133
← previous block
next block →
recent activity
Analyzing
Block #86,629,133
10 transactions · 7 stateful · 2026-07-09 13:08:17 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,629,133
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
#3
permit2TransferAndMulticall
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x6a4f9db9
#7
setData
#8
0xb8024e9b
#9
0x39435dac
#4
permit2TransferAndMulticall
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fc8cab4…6f98
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x146d7940…d263
0x754704…b603
4 touches
1 conflict
0x421c32c1…4629
0x754704…b603
4 touches
1 conflict
0x5a1cd68f…4125
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x566dc83d…6de3
0x34b655…2a6f
2 touches
0 conflicts
0x5cab620b…1c82
0x34b655…2a6f
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-MON/USDC
1 conflict on slot
0x3fc8cab469…256f98
Audit this contract →
← previous block
·
next block →
recent activity