pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,583,526
← previous block
next block →
recent activity
Analyzing
Block #87,583,526
10 transactions · 6 stateful · 2026-07-13 23:30:19 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,583,526
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
verifyOracleProofV2
#6
0x6a557583
#7
setData
#8
0x73f507…d280
#9
0xaaade2…22e0
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4b8f2c5…f54d
0x34b655…2a6f
4 touches
1 conflict
0x82e3f65a…d23c
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc7981744…932f
0x34b655…2a6f
4 touches
1 conflict
0xd16f1746…3ecc
0x34b655…2a6f
4 touches
1 conflict
0xd35fa247…3e18
0x34b655…2a6f
4 touches
1 conflict
0xe2607c11…8fa7
0x34b655…2a6f
4 touches
1 conflict
0x04c1c529…0ee1
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
0xe4b8f2c50f…c2f54d
Audit this contract →
← previous block
·
next block →
recent activity