pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,504,024
← previous block
next block →
recent activity
Analyzing
Block #86,504,024
10 transactions · 8 stateful · 2026-07-08 23:10:35 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,504,024
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#4
0x57368ddf
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0xc1ae1f…aafa
#9
0xc7e3ec2c
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0cd78001…c8bc
0x34b655…2a6f
2 touches
0 conflicts
0x2b7950c1…2342
0x34b655…2a6f
2 touches
0 conflicts
0x37ee30c9…9e70
0x34b655…2a6f
2 touches
0 conflicts
0x6083af24…a0df
0x34b655…2a6f
2 touches
0 conflicts
0x64a785e4…0110
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
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity