pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,493,955
← previous block
next block →
recent activity
Analyzing
Block #86,493,955
11 transactions · 8 stateful · 2026-07-08 22:03:27 UTC
Parallelism
73
/100
Blocked
38
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,493,955
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
transfer
· blocks 2
#6
setData
#7
0xae8ab9…caa7
#8
0xff2dc0…12ae
#9
execOrders
· blocks 1
#4
transfer
· blocks 1
#10
execOrders
#5
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0dd44476…ef40
0x34b655…2a6f
2 touches
0 conflicts
0x2f22a3f3…2a56
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x522e20b4…fbc4
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:
USDC (USDC)
3 conflicts on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity