pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,944,738
← previous block
next block →
recent activity
Analyzing
Block #86,944,738
8 transactions · 6 stateful · 2026-07-11 00:18:24 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,944,738
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execPerpOps
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcadf8b62…6261
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04f3bd2a…8c2a
0x34b655…2a6f
2 touches
0 conflicts
0x2029b74e…c206
0x34b655…2a6f
2 touches
0 conflicts
0x35d95fb0…db9e
0x34b655…2a6f
2 touches
0 conflicts
0x35d95fb0…db9f
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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:
Perpl
1 conflict on slot
0xcadf8b62e9…736261
Audit this contract →
← previous block
·
next block →
recent activity