pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,596,432
← previous block
next block →
recent activity
Analyzing
Block #96,596,432
8 transactions · 6 stateful · 2026-08-16 21:24:55 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,596,432
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
· blocks 2
#4
setData
#6
verifyOracleProofV2
#5
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c090991…010a
0x34b655…2a6f
6 touches
3 conflicts
0xdd1f1c82…80bd
0x34b655…2a6f
6 touches
3 conflicts
0x0fe1e6e0…f553
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd14064d5…6732
0x34b655…2a6f
4 touches
1 conflict
0xd64c1971…1bf2
0x34b655…2a6f
4 touches
1 conflict
0x0fc81850…e472
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e0
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
3 conflicts on slot
0x7c090991b5…92010a
Audit this contract →
← previous block
·
next block →
recent activity