pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,166,118
← previous block
next block →
recent activity
Analyzing
Block #87,166,118
10 transactions · 8 stateful · 2026-07-12 00:57:18 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,166,118
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#7
0x6a52e6e6
#8
setData
#9
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
0xad95efd9…b4cf
0x34b655…2a6f
4 touches
1 conflict
0xd1a8dbe2…ecf7
0x34b655…2a6f
4 touches
1 conflict
0xd526b516…a51a
0x34b655…2a6f
4 touches
1 conflict
0xddbe9a3a…9dba
0x34b655…2a6f
4 touches
1 conflict
0xe85e763f…3b25
0x34b655…2a6f
4 touches
1 conflict
0x64852187…6caf
0x34b655…2a6f
4 touches
1 conflict
0x64852187…6cb0
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
0xaba6578de5…b7bd48
Audit this contract →
← previous block
·
next block →
recent activity