pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,453,190
← previous block
next block →
recent activity
Analyzing
Block #87,453,190
10 transactions · 6 stateful · 2026-07-13 08:57:50 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,453,190
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
· blocks 2
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x3f5c179b
#8
execFwdPositionOps
#9
batchCancelOrders
#3
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2878
0x34b655…2a6f
4 touches
1 conflict
0x875c3459…2879
0x34b655…2a6f
4 touches
1 conflict
0xf0feb15e…420b
0x34b655…2a6f
4 touches
1 conflict
0xb0446875…2b96
0x34b655…2a6f
4 touches
1 conflict
0xab67066e…3eb8
0x34b655…2a6f
3 touches
1 conflict
0x259f3ba0…a139
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
3 conflicts on slot
0x737acb7813…fafce8
Audit this contract →
← previous block
·
next block →
recent activity