pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,332,572
← previous block
next block →
recent activity
Analyzing
Block #87,332,572
9 transactions · 8 stateful · 2026-07-12 19:31:14 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,332,572
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#7
transfer
#8
setData
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb6731c…b151
0x34b655…2a6f
4 touches
1 conflict
0x0a6a5b44…d0e5
0x34b655…2a6f
4 touches
1 conflict
0x0b65d0ba…a344
0x34b655…2a6f
4 touches
1 conflict
0x0b65d0ba…a345
0x34b655…2a6f
4 touches
1 conflict
0x447a777e…593e
0x34b655…2a6f
4 touches
1 conflict
0x89d64735…5a63
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
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
0xfcb6731c4b…b9b151
Audit this contract →
← previous block
·
next block →
recent activity