pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,312,022
← previous block
next block →
recent activity
Analyzing
Block #87,312,022
15 transactions · 14 stateful · 2026-07-12 17:13:47 UTC
Parallelism
87
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,312,022
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
forward
#3
forward
#4
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
forward
#9
forward
#10
forward
#11
forward
#13
0x6a53cbc2
#14
setData
#12
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f15f74f…8d72
0x34b655…2a6f
4 touches
1 conflict
0x1737ef68…1e55
0x34b655…2a6f
4 touches
1 conflict
0x0f15f74f…8d71
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x856d2776…04c9
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x138ed846…08c9
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x0f15f74f70…258d72
Audit this contract →
← previous block
·
next block →
recent activity