pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,135,959
← previous block
next block →
recent activity
Analyzing
Block #86,135,959
12 transactions · 10 stateful · 2026-07-07 06:12:08 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,135,959
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
#3
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#6
batchUpdate
#7
execOrders
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
setData
#11
execOrders
#4
execFwdPositionOps
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
0x6762cac2…3fb0
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xcdce9165…2a57
0x34b655…2a6f
3 touches
1 conflict
0x247e8081…9fb5
0x34b655…2a6f
2 touches
0 conflicts
0x35a9f06c…7689
0x34b655…2a6f
2 touches
0 conflicts
0x425376d1…8979
0x34b655…2a6f
2 touches
0 conflicts
0x52ab164e…d75a
0x34b655…2a6f
2 touches
0 conflicts
0x59a54ff4…d21b
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
0x6762cac28d…f93fb0
Audit this contract →
← previous block
·
next block →
recent activity