pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,792,707
← previous block
next block →
recent activity
Analyzing
Block #87,792,707
10 transactions · 8 stateful · 2026-07-14 22:49:28 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,792,707
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
setData
#8
0x34653439
#9
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x80656e3b…9240
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
2 touches
0 conflicts
0x32aabf84…0eb8
0x34b655…2a6f
2 touches
0 conflicts
0x3b64bdff…4cb1
0x34b655…2a6f
2 touches
0 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
2 touches
0 conflicts
0x5655f5c3…6b75
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
0x08636046fc…69e60f
Audit this contract →
← previous block
·
next block →
recent activity