pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,619,857
← previous block
next block →
recent activity
Analyzing
Block #96,619,857
12 transactions · 11 stateful · 2026-08-16 23:22:45 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,619,857
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6c05cd2b
#2
0xa96df62f
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 1
#5
executeBatch
#6
0x3f5c179b
#7
0x3f5c179b
#9
0xed82b078
#10
execFwdPositionOpsV2
#11
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x064fb5…6207
2 touches
0 conflicts
0x00000000…0001
0x064fb5…6207
2 touches
0 conflicts
0x00000000…0008
0x064fb5…6207
2 touches
0 conflicts
0x79e5e792…dfe6
0x11ed3b…2c96
2 touches
0 conflicts
0xfd4df3d8…23fe
0x11ed3b…2c96
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
1 conflict on slot
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity